email-agent-mcp vs Gmail API

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.

Gmail API 90

Graded on the REST API with the hosted lines. The Google Workspace Status Dashboard lists Gmail with an incidents feed that goes back to October 2025 (20). In the 90 days to 1 November 2026 the feed, re-read that day, has one Gmail entry, a low-severity notice from 18 to 24 September about the Gmail Android app, with no entry that touches the service or the API, and its newest entry for any product began on 25 September. The last service disruption for Gmail was 56 minutes on 31 May 2026, across several Workspace products. The dashboard tracks the Gmail product, not the API alone (30). 1,200,000 quota units a minute per project, 6,000 a minute per user and 80,000,000 a day per project, with a unit cost for every method, re-read on 1 November (15). 403 and 429 rate errors with a truncated exponential backoff formula, and 429s for sending and bandwidth limits that carry a retry time. messages.send has no idempotency key, and the error guide says a 200 response doesn't mean the mail was sent (10). The Workspace SLA (last modified 31 August 2026, re-read on 1 November) covers Gmail at 99.9 per cent but measures downtime in the user web interface and doesn't name the API, read the same way as for Drive (5). The REST API is GA. The MCP server is a developer preview (10).

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.

Gmail API 82

Closed service under the Google APIs Terms of Service (last modified 9 November 2021), with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum commits Google to delete Workspace customer data within a maximum of 180 days of a deletion, and the Workspace developer policy limits what third-party apps may do with Gmail data, including no transfer for advertising and no training of general models. We found no retention statement for personal accounts' data reached through the API, and didn't read the privacy policy text, per the 8 October check (20). Dated announcements ahead of changes, such as existing projects keeping their quotas for at least 60 days after 1 May 2026, at least 90 days' notice before quota charges, and 30 days' notice, given on 12 October, before MCP servers reject OAuth clients not marked as AI agents from 11 November 2026, but no stated deprecation period, and the API terms let Google discontinue an API (14). The Workspace sub-processor list, last modified 19 October 2026 (23 July on 17 October), names third-party sub-processors with the country each processes in, and covers Gmail as a Core Service for Workspace tenants (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.

Gmail API 35

No x402, MPP or L402 (0). Free within published quotas, with a unit cost for every method, but the price for use above 80,000,000 units a day, planned for later in 2026, isn't published on the quota page on 1 November, which still promises at least 90 days' notice (15). No charge for standard use and no card needed to enable the API (20). A person creates a Cloud project and an OAuth consent screen, a user consents in a browser, and a public app with restricted scopes goes through verification and a security assessment (0).

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.

Gmail API 81

OAuth 2.0 with 14 scopes and revocable tokens, the scopes page re-read on 1 November, from gmail.labels and gmail.send up to the full https://mail.google.com/ scope. The discovery document, revision 20261026, still lists access_token and oauth_token as query parameters, and Google's OAuth guide, re-read on 1 November, shows the query string as an alternative while calling the header preferable, so the checklist's 10-point deduction applies (30 less 10, 20). gmail.readonly, gmail.metadata (headers and labels, no bodies), gmail.labels and gmail.send for least privilege, and permanent delete only under the full scope. Nothing in the API confirms a send or a delete, and every scope that reads mail is restricted (17). The MCP guide warns about indirect prompt injection through email, requires screening of prompts and responses with Model Armor or a documented alternative, and tells operators to review actions. The REST guides say nothing on it (12). Workspace OAuth log events record the API name, method, OAuth client ID and scopes, with the investigation tool limited to higher editions, and no per-call log for personal accounts was found (12). security.txt valid to 2030 with the Google VRP, and the Google Workspace SOC 2 Type II reports, issued quarterly, list Gmail and the Gmail REST API in scope. Apps holding restricted data must pass a CASA assessment every 12 months (20).

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.

Gmail API 87

Google publishes a discovery document, not OpenAPI, which is a machine-readable contract all the same, at revision 20261026 with 79 methods on 1 November. The preview MCP server's 23 tools each carry typed input and output schemas (25). No llms.txt, and developers.google.com/llms.txt, /workspace/llms.txt and /workspace/gmail/llms.txt returned 404 on 17 October, but doc pages return Markdown (the quota, scopes, release notes and error pages did on 1 November) when .md.txt is appended to the URL, which we found no index or link advertising, read as for Drive, Sheets and Forms (5 of 10). Method descriptions say what each call does and sometimes what to call in its place, such as messages.delete pointing to messages.trash, and the MCP tool descriptions name the tool to use first (16). Typed parameters with enums such as format and defaults such as userId=me, but a sent message is one base64url RFC 2822 string in raw and search is one free-text q string (11). An error guide with a JSON sample and a fix for each reason, and code samples across the guides (15). v1 in the path and dated release notes, though the last entry for the core API is 1 May 2026, the 12 October entry concerns the MCP server, and the growth of the MCP server from 10 tools to 23 isn't recorded there (15).