Connect over MCP

MailMoose runs an MCP server. Point any MCP-capable agent at it, sign in once in your browser, and it can read, search, and send your mail from inside the chat you are already using.

The one line setup

Paste this into your agent's chat, not a terminal:

set up https://mailmoose.dev/SKILL.md

The agent fetches that page and writes its own configuration, whatever client it happens to be. You still approve the connection yourself afterwards, in a browser. Nothing is copied or typed by hand.

Set it up by hand

If you would rather write the configuration yourself, these are the only facts you need:

Claude Code

claude mcp add --transport http --scope user mailmoose https://mailmoose.dev/api/mcp

Cursor, Windsurf, VS Code, and most other editors want the same address in their own mcpServers (or servers) configuration file. See Connect Claude Code for the exact file and shape.

ChatGPT and other hosted assistants take the address in a connector settings screen rather than a file. See Connect ChatGPT.

What you can do

• List and search conversations across every mailbox you can see
• Read a thread in full
• Reply inside an existing conversation
• Send a new message from one of your addresses
• Connect a domain you own, and get the DNS records it needs
• Check a domain's DNS after you have added those records
• Turn on sending for a domain
• Create a mailbox on a domain you own

Only the tools you approved at sign-in appear. Reading and searching happen without fuss; anything that sends shows you the message first.

Setting up a domain is the one thing an agent cannot finish alone: the records have to be added at your DNS provider, which is somewhere MailMoose has no access to. What it can do is connect the domain, tell you exactly what to add and where, and check it once you have.

Kept safe by design

A reply can only go to the address already in the conversation, a new recipient needs your confirmation the first time, and text from a message you receive is always treated as information, never as an instruction. Full detail in Connect Claude Code.

No browser available

Something headless, or a client that cannot sign in through a browser, can use an API key instead. See API keys.

Common issues

1. The agent cannot see the tools. Restart the client after it registers a new server.
2. Asked to sign in repeatedly. Pick an organization in MailMoose first, then reconnect.
3. Reading works, sending does not. Sending was not among the permissions you approved. Reconnect and approve it.