← Back to directory
A

Atomic-Mail MCP

Community
Programmable email inbox for AI agents
GitHub source repository ↗
★ 263 Stars Category · Other Popular Source revision 4531e329ed16
56FMRS · C
Reliability
8/20
Security and permissions
13/20
Maintenance
12/20
Documentation
13/20
Setup experience
10/20

Atomic Mail provides autonomous email for AI agents using JMAP and proof-of-work signup, enabling hands-free inbox management. It is suitable for automating email workflows but requires attention to security and the alpha-stage limitations.

Read the FMRS scoring method →

Atomic Mail is an email service provider designed for autonomous AI agents. Agents can register and manage their own @atomicmail.ai inbox via the JMAP standard protocol, without human involvement. It uses proof-of-work (PoW) for signup to prevent abuse, and offers multiple integration paths including MCP, CLI, AgentSkill, and more. This repository contains the MCP server, CLI tools, and integrations for Dify, ClawHub, and others.

Tools

register
Registers a new Atomic Mail inbox and obtains an API key.
jmap_request
Sends JMAP requests to read, send, reply, and manage emails.
help
Displays embedded documentation, presets, and troubleshooting information.

Setup

  1. Add the following JSON to your MCP client config (e.g., for Claude Desktop, edit claude_desktop_config.json): set command to npx and args to ["-y", "@atomicmail/mcp-github"].
  2. Restart the client.
  3. Ask your agent to create an inbox (e.g., prompt it to read https://atomicmail.ai and register).
claude_desktop_config.json
{
  "mcpServers": {
    "atomicmail": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-github"
      ]
    }
  }
}

Fit and risk

Best for

  • Workflows where AI agents need their own email inbox for autonomous operation.
  • Automated email handling without human intervention, especially with Claude, Codex, Cursor, etc.
  • Developers who prefer standard protocols (JMAP) to avoid vendor lock-in.

Not for

  • Scenarios requiring human review of every email, since agents can autonomously send and receive.
  • Mission-critical email for enterprises that cannot rely on third-party deliverability guarantees.
  • Organizations that need full control over their email infrastructure or offline operation.

Required permissions

  • Read and write local credential files (default at `~/.atomicmail/credentials.json`).
  • Network access: communicate with Atomic Mail's auth service and JMAP API.
  • Environment variables: may require `ATOMIC_MAIL_API_KEY` to skip registration.

Risks and side effects

  • API keys stored locally could be misused if leaked.
  • Email content is untrusted; agents might be tricked into executing malicious instructions (e.g., phishing).
  • Service is in alpha with storage quotas and rate limits; may be unstable.
  • Dependency on external service; if Atomic Mail is down, agent email functionality is affected.

Troubleshooting

  1. Check that Node.js 20+ or Deno 2.7+ is installed.
  2. Verify MCP client configuration and restart the host.
  3. Check if `~/.atomicmail/credentials.json` exists and has permissions 0600.
  4. If registration fails, try deleting `~/.atomicmail` and re-register.
  5. Use the `help` tool for built-in troubleshooting guidance.

Use cases

Have an AI agent subscribe your inbox to newsletters, read them, and send you a daily digest.
Agent monitors a support inbox, replies to common tickets, and only escalates difficult cases to humans.
Agent sends survey emails, follows up based on replies, and summarizes findings.

Supported clients

Claude DesktopFull support
Claude CodeFull support
CodexFull support
GitHub CopilotFull support
CursorFull support
Kilo CodeFull support