Find the right context
Read conversations, search knowledge and customer records, or review a call transcript through the permissions you choose.
Integrations Message MCP
Message MCPDeveloper preview
Your AI assistant. Your Message workspace.
A developer preview of scoped MCP tools for conversations, customers, calls, knowledge, bookings, Message Team, iMessage, SMS and Verify.
Not full administrative parity. Does not purchase numbers, place calls, issue refunds or provision messaging lines. OAuth account linking is in release testing; live external-client acceptance and public package publication remain pending.
AI & automation
Make the connection useful.
- 01Your MCP client
- 02Approved Message tools
- 03Your workspace
Approve useful actions
Enable customer replies, iMessage sending, booking cancellation or team messages only when your assistant needs them.
Keep product controls
Existing feature access, messaging consent, sender requirements, credits and usage limits continue to apply.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Access
A separate key for each connection, with explicit permissions and revocation in Message.
Actions
Writes require stable request IDs to prevent duplicate dispatch after retries.
Availability
Developer preview for local MCP clients and remote clients with Authorization-header support. ChatGPT account linking and marketplace listings are pending.
Your setup path
Start with one working flow.
- 01
Choose permissions
An administrator opens Connectors → Message MCP and creates a named connection. Start with read-only access.
- 02
Configure your client
Use the HTTPS MCP endpoint or the downloadable local connector. Store the key in the client's secure configuration, never a chat or public website.
- 03
Test before enabling actions
Read a test conversation first. Enable only the action permissions you need and keep your client's confirmation prompts enabled.