CherryMail
Get started
Skip to documentation
Developersv1

Explore the documentation

OverviewGuidesQuickstartGuidesAuthenticationGuidesLimits & errorsGuidesWebhooksGuidesMCP connectionsGuidesRetrieve accountAccount · GET /account/List domainsDomains · GET /domains/Create a domainDomains · POST /domains/Retrieve a domainDomains · GET /domains/{id}/Delete a domainDomains · DELETE /domains/{id}/Get DNS instructionsDomains · GET /domains/{id}/dns/
Search the CherryMail developer documentation
Developers/AI connections
AI connections

CherryMail for MCP clients

Bring scoped email tools to your AI client, with you in control of sending and deletion.

Developer preview
MCP access is gated pending gateway acceptance. The hosted protocol and local bridge are tested against the official MCP SDK. Vendor-specific connection recipes below do not claim verified compatibility for a particular app version.

Connect with hosted OAuth

Add the endpoint below to an MCP client that supports Streamable HTTP and OAuth. Sign in to CherryMail, choose your account and mailboxes, and consent to the requested permissions.

Hosted MCP endpoint
https://cherrymail.net/mcp

The server uses authorization-code OAuth with S256 PKCE, resource-bound tokens, and rotating refresh tokens. Connecting a client does not automatically grant access to every mailbox.

Use the local stdio bridge

For clients that run a local MCP command, download the CherryMail MCP bridge ↗, extract it, and install its dependencies with Bun. Create a Local MCP credential in Integrations.

Install and run the bridge
cd /absolute/path/cherrymail-mcp
bun install
export CHERRYMAIL_MCP_KEY='your-cm_mcp_-credential'
bun run index.ts

The bridge forwards to the same hosted tool implementation and retains the approval policy. The default server is https://cherrymail.net/mcp; CHERRYMAIL_MCP_URL can override it.

Configure your client

Use an absolute path to the extracted bridge. For Codex, export CHERRYMAIL_MCP_KEY in the environment that starts the client. For the JSON configurations, supply the purpose-bound local MCP key through your client’s secure environment settings where supported.

Local MCP client configuration
[mcp_servers.cherrymail]
command = "bun"
args = ["/absolute/path/cherrymail-mcp/index.ts"]
env_vars = ["CHERRYMAIL_MCP_KEY"]

These are connection recipes for local stdio. Hosted OAuth setup varies by client and version; use the hosted URL only where that client supports the required flow.

Review actions in CherryMail

Tools use the cherrymail_ prefix. Reads and drafts run within your grants. Sending and destructive operations create an immutable pending action and return a CherryMail approval link.

  1. Open the approval link and review the exact recipients, message, attachments, or deletion targets.
  2. Approve or reject in CherryMail. The approval expires after ten minutes and can be used once.
  3. Check status with cherrymail_approvals_get. Permissions are rechecked before execution.
Approval is enforced by the server
MCP clients cannot approve on your behalf. An MCP credential cannot call REST endpoints directly to bypass approval. Revocation or membership changes invalidate dependent access.