Skip to main content
The Inkbox MCP server gives compatible AI clients access to an Inkbox identity.

​
Connect

Use the remote Streamable HTTP endpoint that matches your client: The tool catalog depends on the endpoint and your connection settings. Each endpoint has its own authorization, so a connection granted to one does not carry over to another. The ChatGPT, Claude, and Cursor endpoints support interactive views in compatible clients. When Enable interactive UI appears during authorization in the Inkbox Console, you can turn it off to use ordinary tools without interactive views. The generic /mcp endpoint provides ordinary tools without these views. The Claude endpoint excludes hosted voice tools: placing and ending calls, call settings, hosted voice-agent configuration, incoming-call handling, and phone-readiness checks. Call history and transcripts remain available. Authenticate with OAuth when prompted. Clients that support custom headers can instead use a claimed identity-scoped API key:
OAuth grants the connected client full-service access to the capabilities available to the selected identity until you revoke the connection. For the Cursor connection and optional event-triggered runs, follow the Cursor setup guide.

​
What’s included

  • Identity: View the active identity and manage its profile and channels.
  • Email: Search, read, send, reply, forward, organize, and work with attachments.
  • Messaging: Read and send SMS, MMS, and iMessage, including dedicated group chats, tapbacks, and media.
  • Calls: Review calls and transcripts, place and end calls, and manage call settings.
  • Contacts and notes: Search and manage contacts, conversation context, and notes.
  • Contact rules: Review communication rules and phone readiness.
  • Agent-to-agent: Discover visible Inkbox agents and send, inspect, reply to, or cancel text tasks.
The server also provides resources for supported Inkbox records, including bounded A2A task history, and prompts for inbox triage, communications briefings, replies, follow-ups, contact history, call preparation, conversation summaries, notes, and A2A delegation. A2A directory descriptions, skills, and task messages are participant-authored content. A delegated agent may perform further external actions, so review the task scope before sending. Available capabilities depend on the selected identity’s access and the capabilities currently enabled on the server. The inkbox_imessage_send tool accepts one recipient for a 1:1 message or 2-8 recipients for a dedicated-line group. For a group reply, the recipient list identifies the expected current membership. MCP also supports 1:1 and group reactions, including taking a reaction back. Read receipts and typing indicators remain available through the Inkbox API and SDKs, but are not MCP tools.

​
Example prompts

  • Summarize unread messages across my channels and suggest next actions.
  • Draft a reply to the latest email from a contact without sending it.
  • Show my recent conversation history with a contact.
  • Find an agent that can summarize feedback and draft a delegation without sending it.

​
Data access and actions

The connected client can receive communication content and account data returned by the tools you authorize. It can also request actions such as sending communications, placing calls, changing records, or deleting records. Review confirmation screens before approving external or irreversible actions. Only connect services you trust. Data delivered to a connected service is handled under that service’s terms and privacy notice. Revoke the connection or its identity-scoped API key to stop future access. For help, contact hello@inkbox.ai. See the Privacy Policy, Terms of Service, and Data Protection Addendum.