Get a beta invite

MCP setup

The eMailPlane MCP server exposes the email API to MCP clients such as Claude, ChatGPT, Cursor and Codex, with the same token scopes as the REST API. It runs on your server.

Tools

GroupTools
Sendsend, send_preflight, message_get, events_query
Receive and replyreceive, message_read, thread_list, thread_get, wait_for_reply
Deliverabilitysuppression_list, suppression_check, reputation_status, enforcement_list
Templatestemplate_list, template_get, template_create, template_update, template_diff, template_render, template_promote
Domains and mailboxesmail_domain_claim, mail_domain_list, mail_domain_verify, mailbox_create, mailbox_list, mailbox_credential_issue, mailbox_credential_revoke
Domain setupsetup_context, domain_operation_start, domain_operation_get, domain_operation_list, domain_operation_review, domain_operation_resume, domain_operation_cancel
Apps and API keysapp_create, app_get, app_list, app_credential_issue, app_credential_list, app_credential_rotate, app_credential_revoke

A tool only works if your token has the scope it needs, and every decision is made by the API on your server, never by the MCP layer.

Connect over stdio In private beta

In the beta, the MCP server runs on your server as a local process. Your onboarding brief gives the exact command and its two settings: the API address on your server, and a token with only the scopes this agent needs.

Connect over HTTP Coming soon

Each eMailPlane server will publish a remote MCP endpoint on your own domain, using the streamable HTTP transport:

https://mail.<your-domain>/mcp

The endpoint holds no credentials of its own. Each request must carry your token, which it passes to the API on your server, so a request with no token is refused. It is stateless and answers request/response only.

A typical client configuration will look like this:

{
  "mcpServers": {
    "emailplane": {
      "type": "http",
      "url": "https://mail.example.com/mcp",
      "headers": { "Authorization": "Bearer ${EMAILPLANE_TOKEN}" }
    }
  }
}

In Claude Code:

claude mcp add --transport http emailplane https://mail.example.com/mcp \
  --header "Authorization: Bearer $EMAILPLANE_TOKEN"

MCP Registry Coming soon

We will list eMailPlane in the official MCP Registry as com.emailplane/mail, with a remote URL template of https://mail.{domain}/mcp so each customer's client connects to its own server. The draft entry is published at /mcp/server.json.

Good practice for agents