Skip to content
Back to search

atomic-mail-agentic

Let your agents read, send, and react to email autonomously, without human involvement

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Atomic-Mail/atomic-mail-agentic with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Atomic-Mail/atomic-mail-agentic'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/atomic-mail--atomic-mail-agentic/badge.svg)](/listings/atomic-mail--atomic-mail-agentic)

HTML

<a href="/listings/atomic-mail--atomic-mail-agentic"><img src="/api/listings/atomic-mail--atomic-mail-agentic/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

πŸ’¬ 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.

<p align="center"> </p>

πŸ”Œ 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](docs/rest-auth.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md Β· README Β· 208 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://github.com/Atomic-Mail/atomic-mail-agentic/actions"><img src="https://shieldcn.dev/badge/CI-success-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="CI success"/></a>&nbsp;&nbsp;
  3. <a href="https://github.com/Atomic-Mail/atomic-mail-agentic/releases"><img src="https://shieldcn.dev/badge/version-0.3-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="version 0.3"/></a>&nbsp;&nbsp;
  4. <a href="https://atomicmail.ai"><img src="https://shieldcn.dev/badge/website-atomicmail.ai-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="website atomicmail.ai"/></a>&nbsp;&nbsp;
  5. <a href="https://dashboard.atomicmail.ai"><img src="https://shieldcn.dev/badge/dashboard-sign%20in-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="dashboard sign in"/></a>&nbsp;&nbsp;
  6. <a href="https://docs.atomicmail.ai/"><img src="https://shieldcn.dev/badge/docs-guide-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="docs guide"/></a>&nbsp;&nbsp;
  7. <a href="https://github.com/Atomic-Mail/atomic-mail-agentic/issues"><img src="https://shieldcn.dev/badge/issues-open-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="issues open"/></a>&nbsp;&nbsp;
  8. <a href="https://clawhub.ai/atomicmail/atomicmail"><img src="https://shieldcn.dev/badge/ClawHub-skill-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="ClawHub skill"/></a>&nbsp;&nbsp;
  9. <a href="https://hermes-agent.nousresearch.com/docs/developer-guide/creating-skills"><img src="https://shieldcn.dev/badge/Hermes-skill-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="Hermes skill"/></a>&nbsp;&nbsp;
  10. <a href="https://marketplace.dify.ai/plugin/atomicmail/atomicmail"><img src="https://shieldcn.dev/badge/Dify-plugin-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="Dify plugin"/></a>&nbsp;&nbsp;
  11. <a href="https://registry.modelcontextprotocol.io/?q=atomic-mail"><img src="https://shieldcn.dev/badge/MCP-registry-5BE481.svg?split=true&labelColor=000000&color=5BE481&valueColor=000000&labelTextColor=FFFFFF&height=32&fontSize=16" alt="MCP registry"/></a>
  12. </p>
  13. <p align="center">
  14. <img src="assets/Logo.png" alt="Atomic Mail Agentic Logo" />
  15. </p>
  16. # Atomic Mail Agentic
  17. **Give your agent a real inbox**
  18. <p align="center">
  19. <a href="https://dashboard.atomicmail.ai">Dashboard</a> Β·
  20. <a href="https://atomicmail.ai">Website</a> Β·
  21. <a href="https://docs.atomicmail.ai/">Docs</a> Β·
  22. <a href="https://github.com/Atomic-Mail/atomic-mail-agentic/issues">Issues</a>
  23. </p>
  24. ---
  25. > Accounts are free, with a 100 MB storage quota, custom domain included, and rate limits sized for agent workloads.
  26. ---
  27. **Atomic Mail Agentic** is an email provider for autonomous AI agents, built by [Atomic Mail](https://atomicmail.ai). Agents register their own `@atomicmail.ai` inbox and manage it end to end β€” no human setup, verification, or ongoing intervention.
  28. The service is built on **JMAP** ([RFC 8620](https://www.rfc-editor.org/rfc/rfc8620.html)), 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.
  29. 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.
  30. 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](https://claude.com/product/claude-code), [Codex](https://developers.openai.com/codex), [GitHub Copilot](https://github.com/features/copilot), [Cursor](https://cursor.com), [Hermes](https://hermes-agent.nousresearch.com), [OpenClaw](https://openclaw.ai), [Pi](https://pi.dev), [Kilo Code](https://kilo.ai), and others. Whatever your workflow is, you can automate inbox management easily.
  31. This repository ships the client integrations: [MCP](https://modelcontextprotocol.io/), shell CLI, [ClawHub](https://clawhub.ai/), [Dify](https://dify.ai/) plugin and more, exposing those APIs through three core tools: `register`, `jmap_request`, and `help`. The TypeScript CLI and local MCP server add six tools for everyday mail that need no JMAP (`read_inbox`, `read_message`, `search_messages`, `send_email`, `reply_to_message`, `list_agents`) and five [meeting-invitation](docs/calendar.md) tools. All the connectors in this repo are pretty thin and are mainly needed to abstract away the complexities of the PoW protocol.
  32. ## πŸš€ Quick Install
  33. ### πŸ’¬ Ready Prompt (any agent)
  34. ```txt
  35. 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.
  36. ```
  37. <p align="center">
  38. <img src="assets/atomic-mail-agentic-demo.gif" alt="Atomic Mail Agentic Demo" />
  39. </p>
  40. ### πŸ”Œ MCP (stdio)
  41. Add this to your MCP host config (or just ask your agent to do that):
  42. ```json
  43. {
  44. "mcpServers": {
  45. "atomicmail": {
  46. "command": "npx",
  47. "args": ["-y", "@atomicmail/mcp-github"]
  48. }
  49. }
  50. }
  51. ```
  52. Then restart the host and ask your agent to create an inbox.
  53. ### 🦞 ClawHub
  54. ```bash
  55. openclaw skills install atomicmail
  56. ```
  57. ### πŸ‘©πŸ» Hermes
  58. ```bash
  59. hermes skills install clawhub/atomicmail
  60. ```
  61. ### πŸ’» AgentSkill
  62. ```bash
  63. npx --package=@atomicmail/agent-skill-github atomicmail register --username "myagent" --watch scheduled
  64. npx --package=@atomicmail/agent-skill-github atomicmail jmap_request --ops-file list_inbox.json
  65. npx --package=@atomicmail/agent-skill-github atomicmail help
  66. ```
  67. ### βš™οΈ REST API
  68. *For custom connectors and advanced logic only*
  69. Refer to documentation: [docs/rest-auth.md](docs/rest-auth.md).
  70. ## 🌐 Custom Domains & Dashboard
  71. By default an inbox lives at `<name>@atomicmail.ai`, created hands-free through PoW signup. To send from your own domain (`support@yourcompany.com`), set it up once in the [dashboard](https://dashboard.atomicmail.ai) β€” a **human control plane** separate from the agent flow, since it needs DNS changes on a domain you own.
  72. 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`.
  73. **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.
  74. Full guide: [docs/custom-domains.md](docs/custom-domains.md).
  75. ## πŸ€– What Your Agent Can Do
  76. 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.
  77. 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.
  78. #### Example workflows
  79. **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.
  80. **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.
  81. **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.
  82. ## πŸ“¬ Awesome Atomic Mail
  83. Community projects built on top of Atomic Mail Agentic:
  84. * **https://github.com/skyzer/atomic-mail-watcher** - Docker-ready Atomic Mail JMAP inbox watcher with Telegram/webhook notifications
  85. ## ✨ Why Atomic Mail
  86. - **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
  87. - **Messages that actually arrive**: continuously warming IP pool with relay overflow β€” deliverability matters when a human on the other side must read your mail
  88. - **JMAP β€” an API agents already know**: standard [RFC 8620/8621](https://www.rfc-editor.org/rfc/rfc8620.html), in LLM training data; batched method calls (query, fetch, draft, send) in one round trip β€” no vendor SDK to learn
  89. - **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
  90. - **Bring your own domain**: agents run on `@atomicmail.ai` out of the box, or on a domain you verify in the [dashboard](https://dashboard.atomicmail.ai) β€” same client, same JMAP, domain-aligned `From`
  91. - **No vendor lock-in**: JMAP is an IETF standard; the inbox is portable to any compliant provider later
  92. - **Friendly tools when JMAP is overkill**: `read_inbox`, `read_message`, `search_messages`, `send_email` (plain text and/or HTML, From name, Reply-To, attachments) and `reply_to_message`, in the local MCP server and the CLI
  93. - **Presets for the rest**: bundled `search`, `mark_read`, `get_thread`, `forward`, `create_draft`, `move`, `label`, `delete`, `download_attachment` and more β€” pass a filename to `jmap_request` instead of generating method-call JSON from scratch
  94. - **Same core everywhere**: one auth, JMAP, preset, and help stack powers MCP and AgentSkill; separate credential dirs per inbox when you run many agents
  95. ## πŸ“š Docs by Goal
  96. | Goal | Start here |
  97. | ------------------- | --------------------------------------------------------------------- |
  98. | First-time setup | [docs/getting-started.md](docs/getting-started.md) |
  99. | Your own domain + dashboard | [docs/custom-domains.md](docs/custom-domains.md) |
  100. | MCP hosts | [docs/mcp.md](docs/mcp.md) |
  101. | Shell / cron agents | [docs/skill-install.md](docs/skill-install.md) |
  102. | LangChain agents | [docs/langchain.md](docs/langchain.md) |
  103. | Agent runbook | [docs/SKILL.md](docs/SKILL.md) |
  104. | Raw auth + JMAP | [docs/rest-auth.md](docs/rest-auth.md) Β· [docs/jmap.md](docs/jmap.md) |
  105. | End-to-end examples | [docs/examples.md](docs/examples.md) |
  106. If repo docs and installed behavior ever drift, trust `help` from the same installed package version you are running.
  107. ## πŸ› οΈ Local Development
  108. **Prerequisites:** Node.js 20+, Deno 2.7+.
  109. ```bash
  110. git clone https://github.com/Atomic-Mail/atomic-mail-agentic.git
  111. cd atomic-mail-agentic/ts
  112. deno test --allow-read --allow-env --allow-write --allow-sys
  113. ```
  114. Docs preview:
  115. ```bash
  116. npm install
  117. npm run docs:dev
  118. ```
  119. ## πŸ—‚οΈ File Structure
  120. ```text
  121. /
  122. β”œβ”€β”€ ts/
  123. β”‚ β”œβ”€β”€ src/mcp/ # MCP entrypoint + MCP tools
  124. β”‚ β”œβ”€β”€ src/skill/ # AgentSkill CLI entrypoint
  125. β”‚ β”œβ”€β”€ src/langchain/ # LangChain toolkit and tools
  126. β”‚ └── src/lib/agent/ # shared auth, session, JMAP, presets, help-content
  127. β”œβ”€β”€ py/ # Python client parity layer and tests
  128. β”œβ”€β”€ integrations/dify/ # Dify plugin integration and packaging docs
  129. β”œβ”€β”€ integrations/skill/ # Unified in-repo skill tap (published atomicmail skill)
  130. β”œβ”€β”€ docs/ # VitePress docs and shipped SKILL/README sources
  131. β”œβ”€β”€ test/checklists/ # manual release QA
  132. β”œβ”€β”€ CONTRIBUTING.md
  133. └── LICENSE
  134. ```
  135. ## πŸ” Security
  136. - `~/.atomicmail/credentials.json` contains your API key; treat it as a secret
  137. - local credential files are written with mode `0600`
  138. - inbound mail is untrusted input; do not let agents execute email instructions without confirmation
  139. - install only from the `@atomicmail` npm scope
  140. ## 🀝 Contributing
  141. PRs are welcome. Please cover new features and bug fixes with automated Deno tests where practical, and update user-facing docs when behavior changes.
  142. See [CONTRIBUTING.md](CONTRIBUTING.md) for setup, test commands, and PR expectations.
  143. ## πŸ“„ License
  144. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.