An email MCP server lets your AI client work the mailbox you already have: search it, read a thread, tidy the inbox, write replies. This is the whole path, including the two places it usually goes wrong.
What you need
A mailbox that gives you an IMAP server on port 993 and an app password. Gmail needs 2-Step Verification turned on before it will create one. Yahoo and Fastmail have their own app-password pages.
Microsoft 365 and Outlook are not on that list. They no longer allow password-based IMAP, so there is no app password to make.
A Busymail account. The trial runs 14 days with no card.
On macOS or Linux, the default connection needs Node, curl and a POSIX shell. On Windows, use the direct HTTP connection further down.
Step 1: connect the mailbox
Sign in and connect the mailbox on the connect form. Give it a label, your address and the app password. For Gmail, Yahoo or Fastmail the IMAP and SMTP details come from the provider preset; for any other provider, also enter the IMAP host on port 993, the SMTP server, its port and security, and the drafts, sent and archive folder names. Busymail syncs in the background and files new mail into bundles as it lands. Nothing changes in your existing mail app, and the mail stays on your server.
Step 2: create a token
Tokens live under Settings, MCP. You pick the access when you create one:
Read: message content, summaries, search and sent mail, and saving an attachment to disk through the local script. Every token has this.
Organise: archive, unarchive, pin and unpin. Archiving moves mail out of your inbox on the server, so it changes what every other mail app shows.
Send: queues mail for you to approve. It can also read what is already queued on the account, including the recipients, subject and body, whichever client queued it.
A token cannot change your settings, password or two-factor, add or remove an account, or create and revoke tokens. Revoke one at any time and the others keep working.
Step 3: add the server to the client
The default connection runs a small script from Busymail on your own machine. That script is what lets files move between your disk and your mail without passing through the AI client. Add this to your client's MCP server configuration, with your token in place of the placeholder:
{ "mcpServers": { "busymail": { "args": [ "-c", "shim=$(mktemp -d)/shim.mjs && curl -fsSL https://busymail.app/mcp-shim -o \"$shim\" && exec node \"$shim\"" ], "command": "sh", "env": { "BUSYMAIL_MCP_URL": "https://busymail.app/mcp", "BUSYMAIL_TOKEN": "bmail_paste_your_token_here" } } } } Add the busymail entry under mcpServers, keeping any servers already there: Claude Desktop keeps that file in Settings > Developer > Edit Config, and Cursor in ~/.cursor/mcp.json.
Restart the client. The server appears with its tools.
If the client cannot run a local script
Point it at https://busymail.app/mcp as a Streamable HTTP MCP server and send the token in an Authorization: Bearer header. Claude Desktop adds a remote server on an individual plan under Connectors, which sits under Plugins after the rename and Customize until the rename reaches you, rather than in the config file. Attaching a file by path needs the local script, and so does any tool that downloads an attachment: the direct connection has no download tool and never writes to your disk. The bytes are still reachable by a client that can make an authenticated request of its own. Over direct HTTP the client sends a file as base64 itself, which keeps attachments well below the 25 MiB Busymail accepts.
The check that fails first
An unauthenticated health check will fail, by design. The endpoint needs the bearer token, so a directory or monitor that probes it without one reports it as stale or invalid. If your client shows a connection error, check the token is in BUSYMAIL_TOKEN or the Authorization header before you conclude the server is down.
What the agent cannot do
It cannot send. Send queues the message, and approval happens in Busymail while you are signed in, so the token that wrote a message cannot approve it. That separation is the reason the token exists apart from your session.
Sources: Busymail's MCP setup at https://busymail.app/mcp-setup, read on 8 November 2026.