Claude has no mail client of its own. mcpemails is the hosted MCP server that gives it one: read, search, send, reply, forward, schedule and organize real mail from claude.ai or Claude Desktop.
Add https://mcpemails.com/api/mcp as a custom connector in Claude, click Connect, and sign in with your mcpemails account. Claude registers itself automatically and asks for the scopes you approve. There is no API key to create and no config file to edit.
Claude runs the standard MCP OAuth flow against this server. It registers itself with RFC 7591 dynamic client registration, so there is no client ID to create, and authorizes with authorization code plus PKCE using S256. No client secret is ever transmitted, and the token carries only the scopes you approve on our consent screen. The access token it receives lasts an hour and refreshes itself; it is listed in Dashboard, API Keys as OAuth: followed by the client name, which is where you revoke the connection.
Everything on this page is a way of getting this URL into Claude.
| Field | Value |
|---|---|
| MCP server URL | https://mcpemails.com/api/mcp |
| Transport | Streamable HTTP (MCP 2025-06-18) |
| Authentication | OAuth 2.1, authorization code with PKCE. No API key. |
Four steps. The first two are the same for every client, the rest are specific to this one.
Sign up at mcpemails.com, no card required, then go to Dashboard, Inboxes, Connect Inbox. Gmail connects with one-click Google sign-in; iCloud, Fastmail, Yahoo, Zoho and Yandex take an app-specific password; anything else connects over plain IMAP and SMTP. The free plan holds one inbox, forever.
In claude.ai or Claude Desktop, open Settings, then Connectors.
Click Add custom connector, paste https://mcpemails.com/api/mcp as the connector URL, then click Add.
Click Connect and sign in with mcpemails to authorize. Approve the scopes you want Claude to hold. No API key needed.
Official Claude documentation for remote MCP servers: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Wondering which mailbox to connect first? See the provider compatibility matrix
Anthropic ships its own Google connector, and it is a different path: one provider, inside one app. A custom connector points Claude at an MCP server instead, which is why the same setup then covers iCloud, Fastmail, Zoho, Yandex and any company IMAP mailbox behind a single URL, and why the identical URL works in Cursor, ChatGPT and the rest.
The consent screen is ours, not a formality. A token issued without send:email cannot send, and a token without delete:email cannot delete, no matter what the model is asked to do. If you want Claude reading and drafting but never sending, leave send:email unticked and grant manage:drafts instead.
There are no webhooks and no push. Claude sees new mail when it makes a call, which means when you ask. A standing instruction like "check for anything from finance before we start" is what turns that into a routine; nothing arrives unprompted.
Not by itself. Claude can reach a mailbox only through a connector, and a custom connector pointed at mcpemails is one way to give it one. Once connected, Claude can list, read, search, send, reply, forward, organize and schedule mail across every inbox you have attached, limited to the scopes you approved.
No. Claude does the OAuth browser flow with this server, registering itself dynamically and authorizing with PKCE. API keys exist for clients that cannot do that, such as Cline and JetBrains AI Assistant, and for scripts.
Gmail over Google sign-in, iCloud, Fastmail, Yahoo, Zoho and Yandex with an app-specific password, and any other mailbox that speaks IMAP and SMTP on the standard ports. The client sees them all through the same connection: your agent calls inbox_list first to discover every connected mailbox and its id, so there are no UUIDs to paste anywhere.
Only if you let it. Sending is gated on the send:email scope, so a key or a token without that scope cannot send at all. On top of that, an inbox owner can require human approval in the dashboard, which holds every send, reply, forward, draft send and scheduled send until a person releases it.
No. Every message is fetched live from your provider for the request that asked for it and handed straight to your client. Only the encrypted OAuth token or app password is kept, so future calls can authenticate. Deleting the inbox in the dashboard, or revoking access at your provider, ends the connection at once.
Yes. Both reach custom connectors from the same Settings, Connectors screen and both hold the same connection, so a mailbox added in one is available in the other. For the terminal, see the separate Claude Code guide.
Connect a mailbox in minutes. One inbox free forever, no card required.