Get an audit

Head to head · Email send · October 2026 research run

Cloudflare Email Service vs Postmark API + MCP

Cloudflare Email Service and Postmark API + MCP score within a point of each other on agent readiness, 67.3 (B) and 66.5 (B). Postmark API + MCP leads on reliability, agent ergonomics and payments & pricing. Both do email send.

Cloudflare Email ServiceCloudflare · HTTP API B67.3/100#212 of 722 Postmark API + MCPPostmark (ActiveCampaign) · HTTP API B66.5/100#235 of 722

Which one, for what

Cloudflare Email Service B

Good for Teams already on Cloudflare DNS and Workers that want transactional sending and inbound handling in one account at a low unit price.

Ahead on

  • Schema & documentation, 89 against 81
  • Security & auth, 77 against 63
  • Maintenance & community, 81 against 65

Watch for

Email Sending has been in public beta since 16 April 2026. Cloudflare's terms let it remove a beta service at any time, and no SLA was found

Postmark API + MCP B

Good for Transactional mail where deliverability and a small, well-annotated MCP matter more than a free tier.

Ahead on

  • Reliability, 60 against 51
  • Agent ergonomics, 79 against 72
  • Payments & pricing, 40 against 30

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No OpenAPI spec and no published request-rate limit

Score by category

CategoryWeight this runCloudflare Email ServicePostmark API + MCPEdge
Reliability16%205160Postmark API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28981Cloudflare Email Service +8
Agent ergonomics13%16.27279Postmark API + MCP +7
Security & auth14%17.57763Cloudflare Email Service +14
Payments & pricing10%12.53040Postmark API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88165Cloudflare Email Service +16
Transparency & trust7%8.87677Postmark API + MCP +1
Negative events≤1500
Total67.3 · B66.5 · B

Facts side by side

FactCloudflare Email ServicePostmark API + MCP
KindHTTP APIHTTP API
VendorCloudflarePostmark (ActiveCampaign)
Hosted endpointhttps://api.cloudflare.com/client/v4https://api.postmarkapp.com
TransportsHTTPHTTP, stdio
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceProprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official cloudflare SDK on npm is Apache-2.0MIT
Tools exposednone24
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-252026-08-12
Terms last updated2025-09-122024-12-10
Privacy policy last updatedno date given2026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity3.8M npm/wk, 364k PyPI/wk57 stars, 1.3M npm/wk
Agent reviewsnone3/5 (2)

Verdicts

Cloudflare Email Service

Cloudflare API tokens can be limited to sending, given an expiry and restricted by IP address, and a public OpenAPI file covers 29 Email Sending operations. Sending is still in beta, with no SLA, no idempotency key and no published daily quota, and it needs a domain on Cloudflare DNS and the Workers Paid plan.

Postmark API + MCP

24 MCP tools, all with readOnlyHint, destructiveHint and idempotentHint, and descriptions that point to alternatives. No OpenAPI spec and no published request-rate limit.

Before you call either

Cloudflare Email Service

  1. POST to https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send with Authorization: Bearer <token>. The body needs to, from, subject and one of html or text
  2. Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the emailSendingAdaptive GraphQL dataset first
  3. On 429 (code 10004) wait for the retry-after header. On 409 sending_not_ready the domain setup is unfinished and nothing was sent
  4. Read result.delivered, result.queued and result.permanent_bounces in the response. A 200 does not mean every recipient was accepted
  5. Keep to 50 recipients across to, cc and bcc, and 5 MiB per message including attachments
  6. For SMTP use smtp.mx.cloudflare.net on port 465 with implicit TLS, username api_token and the API token as password. Port 587 is not supported
  7. By default one suppressed recipient fails the whole send. Turn on Drop suppressed recipients for the domain to send to the rest

Postmark API + MCP

  1. Install @activecampaign/postmark-mcp, never the unscoped postmark-mcp package
  2. Use the token POSTMARK_API_TEST to check a payload without sending
  3. Set MessageStream to outbound for transactional mail and a broadcast stream for bulk
  4. Set WEBHOOK_URL_ALLOWLIST so a misled createWebhook call can't send events to someone else's server
  5. Keep count + offset under 10,000 on message and bounce searches

Questions

Which is better for AI agents, Cloudflare Email Service or Postmark API + MCP?

Cloudflare Email Service and Postmark API + MCP score within a point of each other on agent readiness, 67.3 (B) and 66.5 (B). Postmark API + MCP leads on reliability, agent ergonomics and payments & pricing.

Do Cloudflare Email Service and Postmark API + MCP need an API key?

Both need an API key.

Can an agent call Cloudflare Email Service and Postmark API + MCP without installing anything?

Yes. Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4 and Postmark API + MCP at https://api.postmarkapp.com.

Other comparisons with Cloudflare Email Service or Postmark API + MCP

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