| FMRS | 56 / 100 · C | 74 / 100 · B | 72 / 100 · B |
| Reliability | 8 / 20 | 11 / 20 | 10 / 20 |
|---|
| Security and permissions | 13 / 20 | 15 / 20 | 15 / 20 |
|---|
| Maintenance | 12 / 20 | 17 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 14 / 20 | 14 / 20 |
| 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.
| - Developers needing quick, API-key-free web search capabilities
- Privacy-conscious users who prefer local search execution
- AI application development with Claude Desktop or Claude Code
| - Privacy-conscious developers who want local data storage.
- Researchers who need AI-assisted management of large note collections.
- Users of Markdown editors like Obsidian.
|
| 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.
| - Enterprise applications requiring high-scale, reliable search APIs
- Users needing advanced search features like custom ranking or filters
- Accessing sites blocked by TLS fingerprinting without installing the optional browser backend
| - Users needing cloud sync and mobile access (unless using the paid cloud service).
- Minimalists who want zero configuration.
- Scenarios requiring large-scale vector databases and complex retrieval (local SQLite may be insufficient).
|
| 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.
| - Outbound network access to DuckDuckGo and other websites
- Reads environment variables for SafeSearch, region, and CA certificates
- Optionally reads a CA certificate file (for TLS-intercepting proxies)
| - Read and write to the local filesystem (default: ~/basic-memory).
- Perform file and directory operations (create, edit, delete).
- Access local SQLite database (or Postgres/Milvus if configured).
|
| 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.
| - Search endpoints may occasionally return empty results or errors, especially when blocked
- Content fetching may be subject to SSRF protection, blocking private or loopback addresses by default
- Misuse could lead to rate limiting or IP blocking
| - Tools have write operations that may unintentionally modify or delete notes.
- Edit operations may overwrite existing content, though there are protections.
- Semantic search and reranking features may require model downloads, adding latency.
- Local data backups are the user's responsibility.
|
| Supported clients | Claude Desktop, Claude Code, Codex, GitHub Copilot, Cursor, Kilo Code | Claude Desktop, Claude Code | Claude Desktop, Claude Code, Codex CLI, Cursor, VS Code, ChatGPT, Obsidian |
| Tools | 3 | 2 | 21 |