https://inkbox.ai/mcp/cloudflare to use an Inkbox identity’s email, messaging, calls, contacts, notes, and Agent-to-Agent tools.
Your agent connects to Inkbox’s remote MCP service. You do not need to host an Inkbox server or apply for a marketplace listing to make this direct connection.
Connect with an API key
- Create a claimed identity-scoped API key in the Inkbox Console.
- Add it to your application’s secret bindings as
INKBOX_API_KEY. Keep the value out of source control, browser code, and logs. - Add a connection method to your existing
Agentclass:
- Call
connectInkbox()from your application’s authorized setup flow. Set it up once; the SDK reuses a connection with the same name and URL and persists it across restarts. You do not need to add it for every message. - Wait for the connection to become ready, then expose its discovered tools to your agent’s model using the SDK’s MCP client integration.
X-API-Key, in your agent’s Durable Object storage. Treat that stored connection configuration as a credential.
Use OAuth instead
For user-authorized access, omit theX-API-Key header and connect to the same URL. The SDK manages the OAuth flow. If addMcpServer returns state: "authenticating", send that user to its authUrl to choose an Inkbox organization and identity and approve access.
Configure the SDK’s callback route and public callback host for your deployment, following Cloudflare’s OAuth setup. Confirm that the connection reaches ready after authorization. OAuth access is bound to https://inkbox.ai/mcp/cloudflare; tokens issued for another Inkbox endpoint cannot be reused here.
Each OAuth authorization creates an independent connection. Connecting another
identity—or the same identity again—with the same OAuth client does not disconnect
existing connections. Each connection keeps its own identity access and refresh
credentials. Revoking one connection’s refresh token does not revoke its siblings;
account or organization access changes can still affect multiple connections.
Verify the connection
Callinkbox_identity_get through the discovered tools and confirm the selected identity. Try a read-only action before requesting a send or call. The endpoint provides ordinary MCP tools without interactive MCP views; available actions follow the identity’s access.
See Connect with MCP for the tool capabilities and data-access details.

