Get an audit

Head to head · Email send · October 2026 research run

Cloudflare Email Service vs Mailjet API + MCP

Cloudflare Email Service scores 67.3 (B) on agent readiness against Mailjet API + MCP's 59.4 (C), and leads in 5 of 7 scored categories. Mailjet API + MCP leads on reliability. Both do email send.

Cloudflare Email ServiceCloudflare · HTTP API B67.3/100#212 of 722 Mailjet API + MCPMailjet (Sinch) · HTTP API C59.4/100#430 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 76
  • Agent ergonomics, 72 against 53
  • Security & auth, 77 against 52

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

Mailjet API + MCP C

Good for EU-based senders who want cheap transactional and marketing mail with data kept in the EU.

Ahead on

  • Reliability, 62 against 51

Also in its favour

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

Watch for

The MCP server registers 117 GET-only tools and can't send

Score by category

CategoryWeight this runCloudflare Email ServiceMailjet API + MCPEdge
Reliability16%205162Mailjet API + MCP +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28976Cloudflare Email Service +13
Agent ergonomics13%16.27253Cloudflare Email Service +19
Security & auth14%17.57752Cloudflare Email Service +25
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88179Cloudflare Email Service +2
Transparency & trust7%8.87672Cloudflare Email Service +4
Negative events≤1500
Total67.3 · B59.4 · C

Facts side by side

FactCloudflare Email ServiceMailjet API + MCP
KindHTTP APIHTTP API
VendorCloudflareMailjet (Sinch)
Hosted endpointhttps://api.cloudflare.com/client/v4https://api.mailjet.com/v3.1
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 exposednone117
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-252026-09-14
Terms last updated2025-09-12no date given
Privacy policy last updatedno date given2026-09-29
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 noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity3.8M npm/wk, 364k PyPI/wk255 stars, 177k npm/wk, 245k PyPI/wk
Agent reviewsnone2.5/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.

Mailjet API + MCP

SandboxMode on Send API v3.1 validates a payload without delivering it. The MCP server registers 117 GET-only tools and can't send.

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

Mailjet API + MCP

  1. Set SandboxMode to true on the first sends to check payloads without delivering
  2. Send with POST /v3.1/send and a Messages array, many messages per call
  3. Use the MCP for statistics and contact lookups only, since it can't send
  4. Pass MAILJET_API_KEY as key:secret. The server checks it at startup and exits if it's wrong
  5. On 429, wait and retry. Non-transactional endpoints have much lower limits than send

Questions

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

Cloudflare Email Service scores 67.3 (B) on agent readiness against Mailjet API + MCP's 59.4 (C), and leads in 5 of 7 scored categories. Mailjet API + MCP leads on reliability.

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

Both need an API key.

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

Yes. Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4 and Mailjet API + MCP at https://api.mailjet.com/v3.1.

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