# email-agent-mcp vs Outlook Mail (Microsoft Graph) (slim)

> email-agent-mcp scores 65.9 (B) to Outlook Mail's 57.8 (C) for mailbox access. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/email-agent-mcp-vs-outlook-mail-graph.md (~4,300 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/email-agent-mcp-vs-outlook-mail-graph.json · canonical https://www.anchorterminal.com/compare/email-agent-mcp-vs-outlook-mail-graph
- 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 Outlook Mail (Microsoft Graph)'s 57.8 (C), and leads in 2 of 7 scored categories. Outlook Mail (Microsoft Graph) leads on reliability, schema & documentation and transparency & trust. Both do mailbox access.

- email-agent-mcp: B 65.9, rank #397 of 1510 · https://www.anchorterminal.com/tools/email-agent-mcp.min.md
- Outlook Mail (Microsoft Graph): C 57.8, rank #778 of 1510 · https://www.anchorterminal.com/tools/outlook-mail-graph.min.md
- 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 Payments & pricing, 60 against 35; Maintenance & community, 84 against 76. Also Runs on your own machine; Open source; No incidents deducted, where Outlook Mail (Microsoft Graph) loses 14 points for them.
- Outlook Mail (Microsoft Graph), good for Agents working in Microsoft 365 or Outlook.com mailboxes that need scoped reading, drafting, sending and incremental sync. Ahead on Reliability, 67 against 50; Schema & documentation, 93 against 79; Transparency & trust, 76 against 42. Also A hosted endpoint, with nothing to install.

| Category | email-agent-mcp | Outlook Mail (Microsoft Graph) |
| --- | --- | --- |
| Reliability (16%) | 50 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 93 |
| Agent ergonomics (13%) | 79 | 81 |
| Security & auth (14%) | 67 | 71 |
| Payments & pricing (10%) | 60 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 76 |
| Transparency & trust (7%) | 42 | 76 |

| Fact (where they differ) | email-agent-mcp | Outlook Mail (Microsoft Graph) |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | UseJunior | Microsoft |
| Hosted endpoint | no (local only) | `https://graph.microsoft.com/v1.0` |
| Transports | stdio | HTTP |
| Pricing | Free | Your plan |
| Licence | Apache-2.0 | MIT (SDKs) |
| Tools exposed | 27 | 10 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.UseJunior/email-agent-mcp` | not listed |
| Last release | 2026-11-05 | 2026-10-22 |
| Terms last updated | no document linked | 2025-10-01 |
| Privacy policy last updated | no document linked | 2026-09-01 |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 394 npm/wk | 835 stars, 2.9M npm/wk, 1.6M PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Transparency & trust, Outlook Mail (Microsoft Graph) +34: email-agent-mcp 42 (Apache-2.0 with a LICENSE file (30). SECURITY.md says tokens and mail are handled locally over stdio with no network listener, and the broker README says mail never reaches the broker and refresh tokens aren't stored. The broker has no published privacy policy (22 of 30). No deprecation policy (0). No telemetry was found in the README or package manifests, and none is stated either way (10 of 20). Total 62.); Outlook Mail (Microsoft Graph) 76 (Closed service under the Microsoft APIs terms of use, last updated October 2025, with MIT SDKs (15). Microsoft 365's retention page says deleted customer content is removed within 30 days and within 180 days of a subscription ending, and the Exchange Online residency page names where mailbox content is stored. The privacy statement refused our reader and we didn't read the data protection addendum (20). A written policy of at least 24 months' notice before a v1.0 API or version is retired (versioning page re-read on 1 November), and dated notices such as the Exchange Web Services retirement (20). Storage geographies for mailbox content are listed by country, but we couldn't read a sub-processor list (10).)
- Payments & pricing, email-agent-mcp +25: 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.); Outlook Mail (Microsoft Graph) 35 (No x402, MPP or L402 (0). Mail endpoints aren't on the metered API list, so calls carry no charge, but a work mailbox needs an Exchange Online or Microsoft 365 licence and the plan price page refused our reader (15). Personal Outlook.com accounts work with delegated Mail permissions at no cost and no card (20). A person registers an app in Entra and, for application permissions, an admin consents (0).)
- Reliability, Outlook Mail (Microsoft Graph) +17: 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.); Outlook Mail (Microsoft Graph) 67 (Graded on the v1.0 REST API. A public Microsoft service health page at status.cloud.microsoft (20), per the 8 October check. On 1 November its robots.txt answered an empty 401, so the host is treated as blocked and wasn't read, as for dynamics-365-sales. No readable components or incident history (5). Outlook limits are published at 10,000 requests per 10 minutes, four concurrent requests and 150 MB of uploads per 5 minutes for each app and mailbox pair (throttling page updated 17 September 2026, re-read on 1 November), and Exchange Online caps sending at 30 messages a minute and 10,000 recipients a day (15). 429 responses carry `Retry-After`, with backoff guidance and SDK retry handlers, but sendMail has no idempotency key and returns 202 Accepted before delivery, so a retried send can duplicate (10 of 15). The Online Services SLA (November 2026 edition, read on 1 November) pays credits from 25 per cent below 99.9 per cent uptime for Exchange Online, the paid service every work mailbox needs, but measures downtime as users unable to send or receive email with Outlook Web Access, plus email delivery time, and has no Microsoft Graph entry. Read as microsoft-teams reads the same document's Teams level, measured on the user-facing service and not naming the API (7 of 10). Mail endpoints are generally available on v1.0 (10). 20+5+15+10+7+10 = 67.)
- Schema & documentation, Outlook Mail (Microsoft Graph) +14: 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.); Outlook Mail (Microsoft Graph) 93 (OpenAPI for all of Graph v1.0 in microsoftgraph/msgraph-metadata (25). No llms.txt on learn.microsoft.com, but every reference page we asked for with `Accept: text/markdown` came back as Markdown (10). Reference pages state the purpose of each call, list permissions from least to most privileged and name limits such as the `$filter` and `$orderby` ordering rule and the 1,000-result cap on `$search` (17). Typed properties and enumerations in the metadata, though sendMail also accepts a base64 MIME blob (13). An example request and response on each page, a shared error format and a status code table, with few mail-specific error codes listed (13). v1.0 and beta, a dated changelog and a monthly What's new page updated on 8 October 2026 (15).)
- Maintenance & community, email-agent-mcp +8: 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.); Outlook Mail (Microsoft Graph) 76 (msgraph-sdk-python v1.65.0 on 22 October 2026 (30). Five Python SDK tags since 3 August (v1.61.0 on 5 August to v1.65.0), counted half, plus dated changelog feed entries to 6 October 2026 and What's new entries for August, September and October 2026, so at least three dated changes in 90 days (20). A public changelog, a What's new page updated on 31 October 2026 and SDK issue trackers, but security fixes merged into the JavaScript client on 16 June and 15 October 2026 still haven't reached npm, where 3.0.7 from September 2023 is current (10). Current SDKs in most languages, with the JavaScript client the exception (10). Active tagging on the Python repository, none of it reaching the JavaScript package (6). 30+20+10+10+6 = 76.)