
The mails.ai MCP server gives an AI app 72 tools for your workspace's email: one for every API call except the event stream, the billing portal and the two unsubscribe links. Connect an app by signing in, or with an API key.

Add https://api.mails.ai/mcp as a remote MCP server in Claude, Claude Code, Cursor, Codex or VS Code. The app opens mails.ai in your browser: sign in, choose the workspace and press Allow. There is no key to copy or paste.
In Claude Code, run claude mcp add --transport http mails https://api.mails.ai/mcp, then type /mcp in a session and choose mails to sign in. The MCP docs have the steps for every app, and Settings › Connected apps disconnects an app at any time.
{
"mcpServers": {
"mails": {
"command": "npx",
"args": ["-y", "@mailsai/mcp-server"],
"env": { "MAILS_API_KEY": "mk_live_..." }
}
}
}Use this for an app that cannot sign in, or for a server or CI job with no browser. The block goes in the app's MCP config, and Claude Desktop, Cursor and Windsurf read the same shape. Make the key on the API keys page. Its scopes decide what the tools may do: a key without the send scope has no sending tools.
Sent mail — mails_send, mails_reply and mails_forward, batch sends, reading what was sent and its original email, moving or cancelling a scheduled send, and appealing a refused send.
Received mail — received emails, replies and first-contact mail, their attachments, and mails_test_inbound, which simulates a received email on a test key.
Threads, drafts, labels and search — read, update and delete threads; create, update and send drafts; manage labels; and mails_search_mail across all mail.
Agents — create, update and archive agents, test an agent's forwarding, and read its inbox summary and sending reputation.
Webhooks and events — create, update, test and delete webhook endpoints, rotate a signing secret, list and replay deliveries, and list, read and redeliver events.
Domains, keys and suppression — add, verify and remove custom domains; list, create and revoke API keys; check whether an address is suppressed and allowlist it.
Account — usage for the billing period, mail metrics, audit logs, connected apps, the connected account and the API's health.
Each connection sees only the tools its access allows. An app connected by signing in cannot make API keys or webhooks, and a key without the send scope has no sending tools. The MCP docs list all 72 tools and what each one does.
Use a test key while you are wiring it up. An assistant with a live send tool and an imperfect prompt is exactly the situation test mode exists for.
Open the MCP page