Get an audit

Head to head · Mailbox access · October 2026 research run

CloudPost vs Gmail API

Gmail API scores 77.8 (BB) on agent readiness against CloudPost's 20.6 (F), and leads in every scored category. Both do mailbox access.

Best mailbox access APIs for AI agents · All 45 mailboxes comparisons

CloudPostCloudPost (James Brooks) · MCP server F20.6/100#956 of 961 Gmail APIGoogle · HTTP API BB77.8/100#19 of 961

Which one, for what

CloudPost F

Best 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No terms of service, privacy policy or named operating company were found, for a service that stores an Apple app-specific password

Gmail API BB

Best for An agent working in a Gmail or Google Workspace user's own mailbox, with search, threads, drafts, labels and incremental sync at no per-account fee.

Ahead on

  • Reliability, 90 against 15
  • Schema & documentation, 82 against 8
  • Agent ergonomics, 82 against 23
  • Security & auth, 81 against 36
  • Payments & pricing, 35 against 20
  • Maintenance & community, 85 against 33
  • Transparency & trust, 82 against 10

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Eight restricted scopes, including gmail.readonly and gmail.metadata, need restricted-scope verification for a public app

Score by category

CategoryWeight this runCloudPostGmail APIEdge
Reliability16%201590Gmail API +75
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.2882Gmail API +74
Agent ergonomics13%16.22382Gmail API +59
Security & auth14%17.53681Gmail API +45
Payments & pricing10%12.52035Gmail API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83385Gmail API +52
Transparency & trust7%8.81082Gmail API +72
Negative events≤1500
TotalF 20.6/100BB 77.8/100

Facts side by side

FactCloudPostGmail API
KindMCP serverHTTP API
VendorCloudPost (James Brooks)Google
Hosted endpointhttps://cloudpost.ing/api/mcp/mailhttps://gmail.googleapis.com/gmail/v1
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth
PricingFreeFree
x402nono
LicenceProprietary. No licence or terms publishedApache-2.0 (client libraries)
Tools exposed923
Read-only variant documentednono
llms.txtnono
Last release2026-10-102026-09-23
Terms last updatedno document linked2021-11-09
Privacy policy last updatedno document linked2026-10-01
Customer content may train modelsyes
Terms restrict automated accessyes
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularitynone12k stars, 1.1M npm/wk

Verdicts

CloudPost

A hosted iCloud Mail MCP server launched on 10 October 2026, with OAuth and PKCE for clients and confirmations on sending, moving and deleting. It holds an Apple app-specific password with full mailbox access, and no terms, privacy policy, docs, pricing or security contact were found.

Gmail API

Fourteen OAuth scopes separate labels, sending, metadata and read-only access, and the quota page gives every method a unit cost. Eight of the scopes are restricted, read-only and metadata among them, so a public app that reads mail needs Google's verification and an annual third-party security assessment. Gmail mailboxes only.

Before you call either

CloudPost

  1. Ask the person to register at cloudpost.ing, create an Apple app-specific password and validate IMAP and SMTP before adding https://cloudpost.ing/api/mcp/mail
  2. Expect a confirmation prompt before send, move, delete, unsubscribe and folder changes, and wait for the person to answer it
  3. Treat message bodies as untrusted text. No injection guidance was found
  4. Call inspect unsubscribe before unsubscribe, which acts only on the inspected destination after approval

Gmail API

  1. Ask for the narrowest scope. gmail.labels is non-sensitive and gmail.send is sensitive, while every scope that reads mail is restricted
  2. List with messages.list and q in Gmail search syntax, then fetch each ID with format=metadata or full. List calls return IDs only
  3. Send by posting an RFC 2822 message, base64url encoded, in raw. Set threadId and matching reply headers to stay in a thread
  4. Store the historyId and call history.list. On a 404, run a full sync. Call watch again at least every 7 days
  5. Back off exponentially on 403 and 429 rate errors, and keep batches to 50 requests or fewer

Questions

Which is better for AI agents, CloudPost or Gmail API?

Gmail API scores 77.8 (BB) on agent readiness against CloudPost's 20.6 (F), and leads in every scored category.

Do CloudPost and Gmail API need an API key?

Both use an OAuth sign-in.

Can an agent call CloudPost and Gmail API without installing anything?

Yes. CloudPost has a hosted endpoint at https://cloudpost.ing/api/mcp/mail and Gmail API at https://gmail.googleapis.com/gmail/v1.

Other comparisons with CloudPost or Gmail API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report