A protocol reference, from Beam's docs
By Beam team · Updated
iMessage MCP server: what it gives an agent
An iMessage MCP server connects a compatible AI agent to messaging tools. Beam provides MCP access for Claude, Codex and other supported clients, with permissions for reading, training, publishing, automation, sending and booking.
Choose the connection path
Beam provides MCP and OpenAPI access for authorized AI agents. Its developer documentation describes bearer-header HTTP and a local stdio bridge. Use the transport supported by your client, and keep connection tokens private.
| Capability | How to use it |
|---|---|
| Claude Code | Connect through bearer-header HTTP using the Beam developer access instructions. |
| Codex | Use the Beam documented MCP connection for Codex, with the token in the process environment. |
| Stdio clients | Use the documented local bridge when the client requires stdio. |
| Custom application | Review the OpenAPI contract and API guide for a server-side integration. |
Checked October 6, 2026. See Beam developer access for current client configuration.
Start with a workspace check
- Open Developer access in the intended Beam workspace and create a connection with the permissions you need.
- Store the token privately and configure the client using Beam's documented HTTP connection or stdio bridge.
- Ask the agent to identify the connected workspace without changing anything.
- Read a test conversation and review a draft before enabling sending.
- Grant send permission only for the intended workflow, then test with a contact you control on an active assigned line.
Read and train access are distinct from publishing, automation, sending and booking. A successful connection alone is not permission to send.
Move from a call or CRM event to a text
Use FaceTime Audio for business when the workflow starts with a call. Check two way CRM sync to keep the reply with the intended customer record.
For larger audiences, review outbound and mass texting before granting sending access. Budget, sending capacity and reply ownership still need a plan.
MCP and OpenAPI serve different integration needs
MCP exposes permissioned tools to a compatible agent client. OpenAPI describes the HTTP contract for an application integration. Beam supports both; choose based on where your workflow runs.
Read the Beam iMessage API guide for server-side messaging and signed events. A queued send is not a delivery receipt: check the recorded status and test-device result.
Before you connect
MCP server questions
Can an agent send a real iMessage through Beam?
Yes, with send permission and an active assigned line. Start with a test contact and check the delivery result separately from queue acceptance.
Does MCP access also configure FaceTime Audio?
MCP connects an agent to Beam workspace tools. Confirm FaceTime Audio routing separately with the Beam team before testing a call and follow-up.
Can I connect Codex as well as Claude?
Beam documents MCP connections for Claude Code and Codex. Follow the client-specific instructions in Beam developer access and keep the connection token private.
When should I use OpenAPI instead?
Use the OpenAPI contract when building a server-side HTTP integration. Use MCP when a compatible agent client should work through permissioned workspace tools.
What should I verify before sending?
Verify the connected workspace, permissions, intended recipient and assigned line. Review the message, send to a test contact and inspect the resulting conversation and delivery status.
Sources
Checked October 6, 2026
Start with a conversation
Build your agent on a real business line
Tell our team what you are building. We will walk through the tool catalog and permissions you actually need.
Live sending requires a plan and an assigned dedicated line.
iMessage
Today 9:41 AM
Hi! I would love to hear how your coaching works.
Happy to chat. Would Thursday work for a discovery call?
Thursday sounds great! Looking forward to meeting you.
Blue bubbles. Read receipts. Typing.
Want this for your business?
Try a conversation with the Beam team.
Beam is not affiliated with Anthropic or Apple.
Powered by Beam