Atomic Mail

Name: Atomic Mail
Author: Atomic-Mail

by Atomic-Mailversion 0.3.33i★ –iComputer or cloud

Registry nameio.github.Atomic-Mail/mcp

Install

Overview

Description from the maker (original English)

Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Chat & email
You need to fill in: ATOMIC_MAIL_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: ATOMIC_MAIL_CREDENTIALS_DIR, ATOMIC_MAIL_API_KEY, ATOMIC_MAIL_AUTH_URL, ATOMIC_MAIL_API_URL, ATOMIC_MAIL_INBOX_DOMAIN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.atomicmail.ai/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "atomic-mail": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ],
      "env": {
        "ATOMIC_MAIL_CREDENTIALS_DIR": "your-value",
        "ATOMIC_MAIL_API_KEY": "your-value",
        "ATOMIC_MAIL_AUTH_URL": "your-value",
        "ATOMIC_MAIL_API_URL": "your-value",
        "ATOMIC_MAIL_INBOX_DOMAIN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http atomic-mail https://mcp.atomicmail.ai/mcp

Or run it on your computer

claude mcp add atomic-mail --env ATOMIC_MAIL_CREDENTIALS_DIR=your-value --env ATOMIC_MAIL_API_KEY=your-value --env ATOMIC_MAIL_AUTH_URL=your-value --env ATOMIC_MAIL_API_URL=your-value --env ATOMIC_MAIL_INBOX_DOMAIN=your-value -- npx -y @atomicmail/mcp-modelcontextprotocol

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "atomic-mail": {
      "url": "https://mcp.atomicmail.ai/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "atomic-mail": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ],
      "env": {
        "ATOMIC_MAIL_CREDENTIALS_DIR": "your-value",
        "ATOMIC_MAIL_API_KEY": "your-value",
        "ATOMIC_MAIL_AUTH_URL": "your-value",
        "ATOMIC_MAIL_API_URL": "your-value",
        "ATOMIC_MAIL_INBOX_DOMAIN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "atomic-mail": {
      "type": "http",
      "url": "https://mcp.atomicmail.ai/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "atomic-mail": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ],
      "env": {
        "ATOMIC_MAIL_CREDENTIALS_DIR": "your-value",
        "ATOMIC_MAIL_API_KEY": "your-value",
        "ATOMIC_MAIL_AUTH_URL": "your-value",
        "ATOMIC_MAIL_API_URL": "your-value",
        "ATOMIC_MAIL_INBOX_DOMAIN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.atomicmail.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ATOMIC_MAIL_CREDENTIALS_DIR env
Override default credential directory (~/.atomicmail/)
ATOMIC_MAIL_API_KEY secret env
Existing API key — skips PoW registration
ATOMIC_MAIL_AUTH_URL env
Override auth service base URL
ATOMIC_MAIL_API_URL env
Override JMAP API base URL
ATOMIC_MAIL_INBOX_DOMAIN env
Default inbox domain when inboxId has no @ (default: atomicmail.ai)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Atomic-Mail, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 82 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1768 servers in this category
Published to the registry more recently than 88% of the other 1768 servers in this category
Basic checks equal to or better than 100% of the other 1768 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Atomic Mail safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ATOMIC_MAIL_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.33) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Atomic Mail Agentic

Give your agent a real inbox

Dashboard · Website · Docs · Issues

Accounts are free, with a 100 MB storage quota, custom domain included, and rate limits sized for agent workloads.

Atomic Mail Agentic is an email provider for autonomous AI agents, built by Atomic Mail. Agents register their own @atomicmail.ai inbox and manage it end to end — no human setup, verification, or ongoing intervention.

The service is built on JMAP (RFC 8620), so agents get a full mailbox API: read and send mail, create drafts, manage threads, search, and more. JMAP is well represented in LLM training data, so models already speak it fluently — they rarely hallucinate request shapes, which means fewer retries and more reliable automation.

Access is gated by a novel proof-of-work ([PoW](https://en.wikipedia.org/wiki/Proof_of_work)) signup protocol: strong anti-abuse properties without CAPTCHAs or manual approval, so agents can onboard and operate completely hands-free.

Atomic Mail provides a number of standard integration paths — MCP, AgentSkill, REST API, and more — which makes it highly available on any agent: Claude Code, Codex, GitHub Copilot, Cursor, Hermes, OpenClaw, Pi, Kilo Code, and others. Whatever your workflow is, you can automate inbox management easily.

This repository ships the client integrations: MCP, shell CLI, ClawHub, Dify plugin and more, exposing those APIs through three core tools: register, jmap_request, and help (the TypeScript CLI and local MCP server add five meeting-invitation tools). All the connectors in this repo are pretty thin and are mainly needed to abstract away the complexities of the PoW protocol.

🚀 Quick Install

💬 Ready Prompt (any agent)

Read the instruction at https://atomicmail.ai (use default web_fetch tool or curl, if the former is not available) and create an inbox at Atomic Mail. Before creating ask for my preferred username. Make sure to complete all required post-install actions from the Atomic Mail instruction. Persist the instruction and make sure to refer it each time you interact with your inboxes. Usually standalone agents (e.g. Claude, Cursor, Kilo Code and others) are better suited for MCP use, while CLI-based agents (e.g. Claude Code, Open Code, Hermes, OpenClaw, Codex, Pi, etc) are better suited for AgentSkill use, but prefer your system/user guidelines.

🔌 MCP (stdio)

Add this to your MCP host config (or just ask your agent to do that):

"mcpServers": { "atomicmail": { "command": "npx", "args": ["-y", "@atomicmail/mcp-github"] } } }

Then restart the host and ask your agent to create an inbox.

🦞 ClawHub

openclaw skills install atomicmail

👩🏻 Hermes

hermes skills install clawhub/atomicmail

💻 AgentSkill

npx --package=@atomicmail/agent-skill-github atomicmail register --username "myagent" --watch scheduled

npx --package=@atomicmail/agent-skill-github atomicmail jmap_request --ops-file list_inbox.json npx --package=@atomicmail/agent-skill-github atomicmail help

⚙️ REST API

*For custom connectors and advanced logic only*

Refer to documentation: docs/rest-auth.md.

🌐 Custom Domains & Dashboard

By default an inbox lives at @atomicmail.ai, created hands-free through PoW signup. To send from your own domain (support@yourcompany.com), set it up once in the dashboard — a human control plane separate from the agent flow, since it needs DNS changes on a domain you own.

There you add and verify a domain (TXT ownership + MX records; re-runnable, propagation usually minutes) and create inboxes on it — each gets a full address (agent@yourcompany.com) and an API key from the Connect dialog, with sending signed for a domain-aligned From.

Clients don't change — same jmap_request, presets, and JMAP shapes. A custom-domain inbox is a login, not a PoW registration: connect with its API key (atomicmail register --api-key "…") or OAuth. $INBOX resolves to the real address (agent@yourcompany.com), so self-addressing and From stay correct with no extra config.

Full guide: docs/custom-domains.md.

🤖 What Your Agent Can Do

Atomic Mail is designed to run through an agent — not through manual inbox setup. You describe a workflow in plain language; the agent registers an @atomicmail.ai address, sends and receives mail, and keeps the thread going. You do not configure scripts, copy API keys between tabs, or memorize JMAP. Everything is automagical.

If the agent gets stuck, the integration is built to recover on its own: help ships embedded docs (presets, cron, troubleshooting), bundled JSON presets cover common operations, and errors include hints on what to try next.

Example workflows

Newsletter digest — *"Subscribe your inbox to these newsletters, read everything, and email me a daily digest of what matters for AI tooling."* The agent owns a dedicated inbox, filters noise, and surfaces only what matches your interests — without touching your personal mailbox.

Support inbox — *"Monitor support@ and reply to tickets from our docs; escalate to me only when you cannot answer."* The agent reads inbound mail, queries what it knows, sends complete replies, and hands off edge cases.

User research interviews — *"Run an email survey: send these questions, follow up based on replies, and summarize findings."* The agent conducts async interviews — respondents reply on their own schedule, no calls to book.

📬 Awesome Atomic Mail

Community projects built on top of Atomic Mail Agentic:

https://github.com/skyzer/atomic-mail-watcher - Docker-ready Atomic Mail JMAP inbox watcher with Telegram/webhook notifications

✨ Why Atomic Mail

Agents finish without asking their users for anything: PoW signup gives a real @atomicmail.ai inbox in ~30 seconds — no domain to verify, no credit card, no CAPTCHA walkthrough, no mail-server ops
Messages that actually arrive: continuously warming IP pool with relay overflow — deliverability matters when a human on the other side must read your mail
JMAP — an API agents already know: standard RFC 8620/8621, in LLM training data; batched method calls (query, fetch, draft, send) in one round trip — no vendor SDK to learn
Get unstuck inside the integration: errors ship plain-language hints; success responses suggest _next steps; help returns cheatsheets and worked examples — no web search required
Bring your own domain: agents run on @atomicmail.ai out of the box, or on a domain you verify in the dashboard — same client, same JMAP, domain-aligned From
No vendor lock-in: JMAP is an IETF standard; the inbox is portable to any compliant provider later
Presets when raw JMAP is overkill: bundled send_mail, list_inbox, reply, and more — pass a filename to jmap_request instead of generating method-call JSON from scratch
Same core everywhere: one auth, JMAP, preset, and help stack powers MCP and AgentSkill; separate credential dirs per inbox when you run many agents

📚 Docs by Goal

Goal	Start here
First-time setup	docs/getting-started.md
Your own domain + dashboard	docs/custom-domains.md
MCP hosts	docs/mcp.md
Shell / cron agents	docs/skill-install.md
LangChain agents	docs/langchain.md
Agent runbook	docs/SKILL.md
Raw auth + JMAP	docs/rest-auth.md · docs/jmap.md
End-to-end examples	docs/examples.md

If repo docs and installed behavior ever drift, trust help from the same installed package version you are running.

🛠️ Local Development

Prerequisites: Node.js 20+, Den

Only the beginning is shown; read the rest in the repo

Atomic Mail

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

Atomic Mail Agentic

🚀 Quick Install

💬 Ready Prompt (any agent)

🔌 MCP (stdio)

🦞 ClawHub

👩🏻 Hermes

💻 AgentSkill

⚙️ REST API

🌐 Custom Domains & Dashboard

🤖 What Your Agent Can Do

Example workflows

📬 Awesome Atomic Mail

✨ Why Atomic Mail

📚 Docs by Goal

🛠️ Local Development