# CloudPost vs email-agent-mcp (slim)

> email-agent-mcp scores 65.9 (B) to CloudPost's 21.1 (F) for mailbox access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cloudpost-vs-email-agent-mcp.md (~4,100 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/cloudpost-vs-email-agent-mcp.json · canonical https://www.anchorterminal.com/compare/cloudpost-vs-email-agent-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

email-agent-mcp scores 65.9 (B) on agent readiness against CloudPost's 21.1 (F), and leads in every scored category. Both do mailbox access.

- CloudPost: F 21.1, rank #1452 of 1510 · https://www.anchorterminal.com/tools/cloudpost.min.md
- email-agent-mcp: B 65.9, rank #397 of 1510 · https://www.anchorterminal.com/tools/email-agent-mcp.min.md
- CloudPost, good for A person who wants an agent to triage and answer their own iCloud Mail from Claude or another OAuth-capable MCP client without running an IMAP server locally. Also A hosted endpoint, with nothing to install.
- email-agent-mcp, good for A person who wants an agent working in their own Outlook mailbox, or reading and drafting in Gmail, with guardrails. Ahead on Reliability, 50 against 15; Schema & documentation, 79 against 8; Agent ergonomics, 79 against 23; Security & auth, 67 against 36; Payments & pricing, 60 against 20; Maintenance & community, 84 against 33; Transparency & trust, 42 against 16. Also Runs on your own machine; Open source.

| Category | CloudPost | email-agent-mcp |
| --- | --- | --- |
| Reliability (16%) | 15 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 8 | 79 |
| Agent ergonomics (13%) | 23 | 79 |
| Security & auth (14%) | 36 | 67 |
| Payments & pricing (10%) | 20 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 33 | 84 |
| Transparency & trust (7%) | 16 | 42 |

| Fact (where they differ) | CloudPost | email-agent-mcp |
| --- | --- | --- |
| Vendor | CloudPost (James Brooks) | UseJunior |
| Hosted endpoint | `https://cloudpost.ing/api/mcp/mail` | no (local only) |
| Transports | HTTP | stdio |
| Licence | Proprietary. No licence or terms published | Apache-2.0 |
| Tools exposed | 9 | 27 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.github.UseJunior/email-agent-mcp` |
| Last release | 2026-10-10 | 2026-11-05 |
| Popularity | none | 394 npm/wk |
| Agent reviews | 2/5 (4) | none |

Why the edge:
- Schema & documentation, email-agent-mcp +71: CloudPost 8 (The tool definitions sit behind OAuth sign-in and an iCloud credential, so their JSON Schema could not be read and the contract line scores absent (0). /llms.txt returns 404 and no Markdown docs exist (0). The home page gives each tool a one-line purpose and an example request, and states side effects such as 'without marking them read' and 'after confirmation'. Nothing says when not to use a tool (5 of 20). Input types, enums and required fields are unread (0). Example requests appear for each tool, with no documented errors (3 of 15). No versioning or changelog was found (0). Total 8.); email-agent-mcp 79 (Tools are defined with typed input schemas that the MCP SDK publishes as JSON Schema (25). README in five languages, AGENTS.md, CLAUDE.md and GEMINI.md; no llms.txt, which a local server doesn't need (5 of 10). The README's tool table marks each tool read, write or destructive and states provider limits, such as Gmail deletes removing drafts only (15 of 20). Typed inputs with options such as `list_style` (12 of 15). Setup examples per client and documented error behaviour, such as NOT_SUPPORTED on Gmail and sanitised errors (10 of 15). Semver tags and GitHub Releases (12 of 15). Total 79.)
- Agent ergonomics, email-agent-mcp +56: CloudPost 23 (Context cost. Nine tools by default and eleven with mailbox management, by the home page's count. Their size is unread, and there is no read-only subset (18 of 25). No pagination, limit or filter beyond a text search is documented, and the parameters are unread (0). Error responses are unread. The 401 from the endpoint is JSON with a WWW-Authenticate header that points to the resource metadata, which only covers sign-in (0). Search and read leave read status unchanged, so reads are safe to repeat, and delete marks a message without emptying the mailbox. readOnlyHint and destructiveHint are unread, and no idempotency guidance for send was found (5 of 20). No SDK and no documented defaults (0 of 15). Total 23.); email-agent-mcp 79 (27 tools in the full profile, the 11 to 30 band, plus the `observe` profile as a read-only subset (20 of 25). List and search tools filter and page; we read the tool table, not every parameter (16 of 20). Errors are sanitised and use stable reasons such as NOT_SUPPORTED, failing closed before a Gmail mutation (15 of 20). readOnlyHint and destructiveHint on the tools in source; sends take no idempotency key (16 of 20). One npx command and a setup wizard for OAuth and mailbox choice; TypeScript only (12 of 15). Total 79.)
- Maintenance & community, email-agent-mcp +51: CloudPost 33 (The service launched on 10 October 2026, the day of this check, so the latest change is within 30 days (30). No changelog or dated release entries (0). No public repository, issue tracker, support address or changelog. The site links @jbrooksuk on X as the only contact (3 of 15, closed service). No entry for cloudpost in the official MCP registry search on 10 October 2026 (0). No package or CI to read (0). Total 33.); email-agent-mcp 84 (v0.5.0 was tagged and published on 5 November 2026 (30). Nine npm releases in the 90 days from 8 August, v0.3.0 to v0.5.0 (20). Pull requests up to #234 merged in the history, all by the one maintainer; issue responses couldn't be read through GitHub's API that day (10 of 25). io.github.UseJunior/email-agent-mcp is in the official MCP registry with 0.5.0 marked latest (15). CI, commitlint, semgrep and Codecov workflows (9 of 10). Total 84.)
- Payments & pricing, email-agent-mcp +40: CloudPost 20 (No x402, MPP or L402 on the site, the OAuth metadata or the 401 response (0 of 40). No price is published, and the site does not say the service is free (0 of 20). The registration form asks for a name, an email address and a password and no card, and the app has no billing screen, so a person can start without paying (20). A person registers in a browser, verifies the email, creates an Apple app-specific password and approves the client, so there is no autonomous route (0). Total 20.); email-agent-mcp 60 (Free, Apache-2.0 software with nothing to buy, scored 20 + 20 + 20 by the self-hosted rule. No payment protocol (0 of 40). Total 60.)
- Reliability, email-agent-mcp +35: CloudPost 15 (Graded with the hosted lines. No status page was found on the site or at a linked address (0), so the 90-day record is scored as unreadable (5). No rate limits are published (0). No 429 or retry guidance was found, and nothing says whether a confirmed send is safe to retry (0). No SLA (0). The service is not labelled beta or preview on any page we read, although it launched on the day of this check (10). Total 15.); email-agent-mcp 50 (Graded with the lines for local packages and stdio MCP servers. Installs from the official npm package `email-agent-mcp` with npx, CI runs on Node 20 (20). A CI workflow with Vitest tests, Codecov and a spec-coverage gate; the run results weren't readable through GitHub's API that day, so partial (20 of 25). Open crash and regression issues couldn't be read because GitHub's API refused our requests for its rate limit (0, unchecked). Semver tags from v0.1.7 to v0.5.0 and auto-categorised GitHub Releases as the changelog, with no breaking changes marked in what we read (10 of 15). Pre-1.0 (0). Total 50.)
- Security & auth, email-agent-mcp +31: CloudPost 36 (Credential model. OAuth with the authorisation code grant, PKCE S256, refresh tokens, dynamic client registration and header-only bearer tokens, with applications disconnectable in settings. There is one scope, `mcp:use`, so a client gets the whole tool set, which we score as plain revocable tokens plus 2 for PKCE and header-only delivery. Behind it CloudPost holds an Apple app-specific password, which grants full IMAP and SMTP access and which the site says is encrypted at rest (22 of 30). Least privilege. No read-only mode. The site says sending, moving, deleting, unsubscribing and creating folders require a confirmation from the client, and folder deletion is limited to empty, non-system folders (10 of 20). Prompt injection. Mail is untrusted content. Unsubscribe inspection never scrapes web pages and unsubscribe needs explicit approval, but no injection guidance was found (4 of 15). No per-call log or audit view was found (0). No security.txt (404), disclosure policy, bug bounty or certification was found (0). Total 36.); email-agent-mcp 67 (OAuth to the person's own provider with the scopes each profile needs, tokens in the OS keychain, and an `observe` profile with Microsoft read scopes only. Gmail uses `gmail.readonly` and `gmail.compose`, and its code exchange and refreshes relay through a UseJunior-hosted broker that holds the client secret and says it stores no refresh tokens (25 of 30). Send allowlists, delete off by default behind an operator variable and a caller flag, inbox rules that block forwarding and deletion, and protected system folders (20). Receive allowlists limit whose mail the agent acts on; no guidance on treating message bodies as untrusted was found (9 of 15). No log of tool calls beyond the mailbox's own history (3 of 15). SECURITY.md with private reporting and acknowledgement within 3 business days, semgrep in CI; no bug bounty or advisories (10 of 20). Total 67.)