An iMessage MCP server for your AI agent
Spaces gives your AI agent an MCP server for your iMessage business number (coming soon) at https://api.spacesos.com/mcp/imessage. It lists only your iMessage accounts and the tools that work on iMessage, so the agent stays on that channel. Please read the iMessage notes below before you connect.
Conversations people start
The best fit is answering the texts customers send your business number, and following up with people who asked to hear from you: a booking reminder, a delivery update, a quote. Your agent replies in the same conversation and hands anything sensitive to a person.
What your agent can do on iMessage
These tools are listed in the Spaces docs:
- List conversations, with an option for unread only, and read messages and photos (list_messaging_chats, list_messaging_messages, get_messaging_attachment).
- Reply in a conversation, or text someone new with to.phone (reply_in_chat, start_chat). Text only for now. Before someone replies, the first message must be under 300 characters with no links.
- Schedule a message and run automations (schedule_message, create_routine).
- Check usage against Spaces' per-number limits (get_messaging_usage).
One server per channel, or one for all
https://api.spacesos.com/mcp/imessage is limited to iMessage: an account from another channel is refused, and connect links are for iMessage only. https://api.spacesos.com/mcp covers every channel with the same key.
Pacing and safe retries
Spaces enforces per-account limits for every key and every agent, however the agent is prompted. New accounts warm up over their first week. Over a limit, the API returns 429 with Retry-After, and nothing was sent. Every send needs an Idempotency-Key, and the same key never sends twice.
Set up
- Sign up with your email and the 6-digit code Spaces sends. An agent can do this for you through the onboarding MCP server at https://api.spacesos.com/mcp/start.
- Add a card at checkout. Don't connect an account until checkout is finished.
- Connect iMessage: iMessage is coming soon. Email hello@spacesos.com to hear when it opens; the number will then appear under list_messaging_accounts.
- Create an API key. It starts with spc_live_ and is shown only once, so store it safely.
- Add the iMessage MCP server https://api.spacesos.com/mcp/imessage to your agent, or call the REST API at https://api.spacesos.com/v1.
Connect Claude, ChatGPT, Cursor or Grok
Every client uses the same MCP URL, https://api.spacesos.com/mcp/imessage, with your API key as a Bearer token. Grok, Grok Bot and Cursor can also sign in with OAuth instead of a key.
| Client | How it connects |
|---|---|
| Claude Code | Run claude mcp add with the URL and an Authorization header (below). |
| Claude Desktop | Settings, then Developer, then Edit Config: add the server with mcp-remote and your key, then restart Claude. |
| Claude API | Pass the URL in mcp_servers with your key as authorization_token, and add an mcp_toolset. |
| ChatGPT | Add a custom MCP connector with the URL and the Authorization header. |
| Cursor | Add an MCP server named spaces with the URL and header, or sign in with OAuth. |
| Grok | Use the xAI API's MCP tool with the URL and header, or sign in with OAuth. |
| Grok Bot | Connect with OAuth: no key needed. Grok Bot finds Spaces through the OAuth discovery document and you approve access. |
Claude Code, in one line:
claude mcp add --transport http spaces https://api.spacesos.com/mcp/imessage --header "Authorization: Bearer spc_live_xxxxxxxxxxxxxxxx"OAuth discovery is at https://api.spacesos.com/.well-known/oauth-authorization-server. API keys keep working alongside OAuth.
Who you message
Pricing
FAQ
How do I connect iMessage to Spaces?
iMessage is coming soon. Spaces will set up a dedicated iMessage number for your business, and it will appear in your dashboard. Email hello@spacesos.com to hear when it opens.
Is it my own iMessage?
No. Spaces sets up a new number for your business. Your personal Apple ID is never connected.
What if the customer has an Android phone?
The message arrives as a normal text instead of an iMessage.
Do I need a separate key for the iMessage MCP server?
No. The same API key works on https://api.spacesos.com/mcp/imessage and on https://api.spacesos.com/mcp. Grok, Grok Bot and Cursor can also sign in with OAuth.