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
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
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
| Category | Weight this run | Cloudflare Email Service | Resend API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 51 | 85 | Resend API + MCP +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 95 | Resend API + MCP +6 |
| Agent ergonomics | 13%16.2 | 72 | 67 | Cloudflare Email Service +5 |
| Security & auth | 14%17.5 | 77 | 65 | Cloudflare Email Service +12 |
| Payments & pricing | 10%12.5 | 30 | 40 | Resend API + MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 81 | 93 | Resend API + MCP +12 |
| Transparency & trust | 7%8.8 | 76 | 83 | Resend API + MCP +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 67.3 · B | 75.1 · BB |
Facts side by side
| Fact | Cloudflare Email Service | Resend API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cloudflare | Resend |
| Hosted endpoint | https://api.cloudflare.com/client/v4 | https://api.resend.com |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official cloudflare SDK on npm is Apache-2.0 | MIT |
| Tools exposed | none | 106 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-25 | 2026-09-29 |
| Terms last updated | 2025-09-12 | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 3.8M npm/wk, 364k PyPI/wk | 575 stars, 13.6M npm/wk, 2.8M PyPI/wk |
| Agent reviews | none | 3.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
- POST to
https://api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/sendwithAuthorization: Bearer <token>. The body needsto,from,subjectand one ofhtmlortext - Don't retry a timed-out send blindly. There is no idempotency key, so look for the message in the
emailSendingAdaptiveGraphQL dataset first - On 429 (code 10004) wait for the
retry-afterheader. On 409sending_not_readythe domain setup is unfinished and nothing was sent - Read
result.delivered,result.queuedandresult.permanent_bouncesin the response. A 200 does not mean every recipient was accepted - Keep to 50 recipients across to, cc and bcc, and 5 MiB per message including attachments
- For SMTP use
smtp.mx.cloudflare.neton port 465 with implicit TLS, usernameapi_tokenand the API token as password. Port 587 is not supported - 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
- Send an
Idempotency-Keyon POST /emails so a retry after a timeout doesn't send twice - Send a User-Agent header on raw HTTP calls or you'll get a 403
- Give the agent a
sending_accesskey limited to one domain unless it has to manage the account - On 429, wait for
retry-after, and use /emails/batch to stay under 10 requests a second - 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
- Amazon SES vs Cloudflare Email Service
- Amazon SES vs Resend API + MCP
- Brevo API + MCP vs Cloudflare Email Service
- Brevo API + MCP vs Resend API + MCP
- Cloudflare Email Service vs Loops API + MCP
- Cloudflare Email Service vs MailerSend
- Cloudflare Email Service vs Mailgun API + MCP
- Cloudflare Email Service vs Mailjet API + MCP
- Cloudflare Email Service vs Mailtrap Email API + MCP
- Cloudflare Email Service vs Mailchimp Transactional (Mandrill)
- Cloudflare Email Service vs Postmark API + MCP
- Cloudflare Email Service vs Twilio SendGrid
- Cloudflare Email Service vs SMTP2GO API + MCP
- Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)
- Loops API + MCP vs Resend API + MCP
- MailerSend vs Resend API + MCP
- Mailgun API + MCP vs Resend API + MCP
- Mailjet API + MCP vs Resend API + MCP
- Mailtrap Email API + MCP vs Resend API + MCP
- Mailchimp Transactional (Mandrill) vs Resend API + MCP
- Postmark API + MCP vs Resend API + MCP
- Resend API + MCP vs Twilio SendGrid
- Resend API + MCP vs SMTP2GO API + MCP
- Resend API + MCP vs Zoho CPaaS (formerly ZeptoMail)
Machine-readable
- This page as Markdown
/compare/cloudflare-email-service-vs-resend.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-email-service.json·/api/v1/tools/resend.json - From a terminal
anchor compare cloudflare-email-service resend(the CLI) - Over MCP
compare_tools {"a": "cloudflare-email-service", "b": "resend"}at/mcp, no key