Atomic-Mail/atomic-mail-agentic

  
  
  
  
  
  
  
  
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)** 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 tools: register, jmap_request, and help. 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)
🔌 MCP (stdio)
Add this to your MCP host config (or just ask your agent to do that):
Then restart the host and ask your agent to create an inbox.
🦞 ClawHub
👩🏻 Hermes
💻 AgentSkill
⚙️ 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.