Connect Gmail, iCloud, Fastmail, or any IMAP inbox once. Paste one MCP endpoint URL into claude.ai, Claude Desktop, Cursor, or any MCP-compatible agent. OAuth clients connect in a click, no API key setup. Your agent reads, searches, and sends mail live, and the mail it reads is never stored.
The decisions that shaped the product. If any of them stop being true, that's a bug worth filing.
A handful of tools cover the everyday work — inbox_list, email_read (list, read, search) and email_compose (send, reply) — and more advanced tools (email_organize, folder, draft, schedule) are there when you need them. Paste the MCP endpoint URL into claude.ai, Claude Desktop, Cursor, or any MCP-compatible agent.
Every tool call hits your provider in real time: Gmail API, Fastmail JMAP, or IMAP. Message bodies, subjects, and attachments go to the agent and are discarded immediately. We persist one thing per inbox, an encrypted token or app password, so we can make the next call. The one exception is a message you schedule to send later: we hold it until the send time, then keep a record for your history.
When your agent calls email_compose (to send or reply), the message is dispatched via the Gmail API, Fastmail JMAP, or your own SMTP server. Your domain reputation and deliverability stay entirely in your hands. We never relay mail from our own domain.
OAuth 2.0 for Gmail; app-specific passwords for Fastmail, iCloud, Yahoo, Zoho, and Yandex; a generic IMAP / SMTP connector for everything else. Connect multiple inboxes, label them by use case (work-gmail, ops-fastmail, support-imap), and scope each API key to the inboxes you want that agent to reach.
Any MCP client that supports OAuth (claude.ai, Claude Desktop, Cursor, and others) connects automatically via authorization code + PKCE. No API key setup. API keys are there for clients without OAuth and for scripted access. Either way, you revoke any connection from the dashboard in one click.
OAuth tokens and app passwords are AES-256-GCM encrypted before being written to the database. Decryption happens only inside an isolated Edge Function at call time. The encryption key is stored as an environment secret, separate from the database.
A real-time dashboard for every connected inbox, API key, and tool call — so you always know what your agents are doing.
Three steps from sign-up to your agent reading and sending mail.
Sign in and click Connect Inbox. Choose Gmail, iCloud, Fastmail, or any IMAP inbox, then complete OAuth or paste an app password. Credentials are encrypted; the mail your agent reads is never stored.
For an MCP client that supports OAuth 2.0 (claude.ai, Claude Desktop, Cursor, and others), paste https://mcpemails.com/api/mcp, click Connect, and authorize. No key needed. For clients without OAuth (Cline, JetBrains, custom scripts), generate a scoped API key in the dashboard instead.
The agent calls tools like email_read() or email_compose(). MCPEmails fetches live from your provider and returns the result. Nothing is cached between calls.
Free is genuinely unlimited. Upgrade for higher burst limits, team features, and support. Switch plans any time.
Everything, unlimited. For everyone building with MCP agents.
For power users running agents around the clock.
For businesses and teams that need roles, SSO, and audit logs.
All plans: the mail your agent reads is fetched live and never stored. OAuth tokens encrypted at rest. Need something custom? Contact us. See full feature comparison →