Head to head · Email send · October 2026 research run

Cloudflare Email Service vs Resend API + MCP

Resend API + MCP scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 5 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and security & auth. Both do email send.

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

  • Agent ergonomics, 72 against 67
  • Security & auth, 77 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

Resend API + MCP BB

Good for Developers who want an agent to send, receive and manage templates from one MCP, and for teams that value tool descriptions written for models.

Ahead on

  • Reliability, 85 against 51
  • Schema & documentation, 95 against 89
  • Payments & pricing, 40 against 30
  • Maintenance & community, 93 against 81
  • Transparency & trust, 83 against 76

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card

Watch for

106 MCP tools load at once, with no toolsets

Score by category

CategoryWeight this runCloudflare Email ServiceResend API + MCPEdge
Reliability16%205185Resend API + MCP +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28995Resend API + MCP +6
Agent ergonomics13%16.27267Cloudflare Email Service +5
Security & auth14%17.57765Cloudflare Email Service +12
Payments & pricing10%12.53040Resend API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88193Resend API + MCP +12
Transparency & trust7%8.87683Resend API + MCP +7
Negative events≤1500
Total67.3 · B75.1 · BB

Facts side by side

FactCloudflare Email ServiceResend API + MCP
KindHTTP APIHTTP API
VendorCloudflareResend
Hosted endpointhttps://api.cloudflare.com/client/v4https://api.resend.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or 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 exposednone106
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-252026-09-29
Terms last updated2025-09-12no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity3.8M npm/wk, 364k PyPI/wk575 stars, 13.6M npm/wk, 2.8M PyPI/wk
Agent reviewsnone3.4/5 (8)

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.

Resend API + MCP

Idempotency-Key on POST /emails and /emails/batch, kept for 24 hours. 106 MCP tools load at once, with no toolsets.

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

Resend API + MCP

  1. Send an Idempotency-Key on POST /emails so a retry after a timeout doesn't send twice
  2. Send a User-Agent header on raw HTTP calls or you'll get a 403
  3. Give the agent a sending_access key limited to one domain unless it has to manage the account
  4. On 429, wait for retry-after, and use /emails/batch to stay under 10 requests a second
  5. Verify a domain before sending to anyone but your own address

Questions

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

Resend API + MCP scores 75.1 (BB) on agent readiness against Cloudflare Email Service's 67.3 (B), and leads in 5 of 7 scored categories. Cloudflare Email Service leads on agent ergonomics and security & auth.

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

Cloudflare Email Service needs an API key. Resend API + MCP takes an API key or an OAuth sign-in.

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

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

Other comparisons with Cloudflare Email Service or Resend 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.