What it does
The server gives an agent its own inbox at an @atomicmail.ai address, created through a proof-of-work signup that needs no CAPTCHA or manual approval. The underlying service exposes a JMAP mailbox API for reading and sending mail, creating drafts, managing threads and searching. The MCP server offers three core tools: register, jmap_request and help. The TypeScript CLI and local MCP server add five meeting-invitation tools. Bundled presets such as send_mail, list_inbox and reply cover common operations.
Someone might reach for it to have an agent run a dedicated inbox for a task, such as collecting newsletters into a daily digest, answering support mail and escalating only unresolved cases, or running an asynchronous email survey and summarising the replies. A custom domain can be used so that mail is sent from the user's own address.
To run it, add the server to an MCP host configuration, restart the host and ask the agent to create an inbox. A custom domain requires a one-time setup in the web dashboard, including TXT and MX DNS records, after which the inbox connects with an API key. A REST API is available for custom connectors.
Limitations and requirements
Custom domains need DNS changes on a domain the user owns and a one-time dashboard setup. Inboxes on custom domains connect with an API key or OAuth, not proof-of-work registration. Accounts have a 100 MB storage quota and rate limits.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source
Atomic Mail
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
v0.3.34As shown on registry.modelcontextprotocol.io when we last read it