@atomicmail/mcp-modelcontextprotocol
Atomic Mail MCP server — local stdio proxy with PoW auth and JMAP, for AI agents. (modelcontextprotocol install channel)
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| jmap_request JMAP method-call batch with automatic auth. Exactly one of: `ops` (JSON string: methodCalls array or full envelope) or `ops_file` (preset path; relative to credential directory). `$VAR` substitution and optional file `attachments`: see `help` topics presets and jmap_cheatsheet. | unknown | unknown | unknown |
| register PoW signup; writes credentials. Usernames are 5–21 characters. Idempotent for the same username and stored inbox. To register another account alongside an existing one, pass `credentials_dir` with a separate path. Returns inbox, accountId, apiKey (first signup only). The `watch` value is your operator's decision, not the agent's — ask them before calling. | read | false | unknown |
| help Built-in agent docs — call early and often, even if you know JMAP. Topics: overview, installation, auth, jmap_cheatsheet, tools, presets, cron, multi_account, troubleshooting, readme. Omit topic for overview; use presets before jmap_request, cron after register, troubleshooting when stuck. | unknown | unknown | unknown |
- repohttps://github.com/Atomic-Mail/atomic-mail-agentic
- packagehttps://www.npmjs.com/package/@atomicmail/mcp-modelcontextprotocol
- homepagehttps://atomicmail.ai?utm_source=npm&utm_medium=package&utm_campaign=modelcontextprotocol
- licenseMIT
- adoption270 stars · 82 forks
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
Add the “as seen on MCPExplorer” badge to your README. 
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →