Get an audit

Head to head · Email send · October 2026 research run

Cloudflare Email Service vs Loops API + MCP

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

Cloudflare Email ServiceCloudflare · HTTP API B67.3/100#212 of 722 Loops API + MCPLoops (Astrodon Corporation) · HTTP API B62.7/100#327 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 82
  • Agent ergonomics, 72 against 66
  • Security & auth, 77 against 40
  • Transparency & trust, 76 against 64

Also in its favour

  • No incidents deducted, where Loops API + MCP loses 3 points for them

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

Loops API + MCP B

Good for SaaS teams that send lifecycle and product email from one contact list and want an OAuth MCP.

Ahead on

  • Reliability, 90 against 51

Also in its favour

  • Free to start without a card

Watch for

No scoped or read-only keys, and no read-only MCP mode

Score by category

CategoryWeight this runCloudflare Email ServiceLoops API + MCPEdge
Reliability16%205190Loops API + MCP +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28982Cloudflare Email Service +7
Agent ergonomics13%16.27266Cloudflare Email Service +6
Security & auth14%17.57740Cloudflare Email Service +37
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88183Loops API + MCP +2
Transparency & trust7%8.87664Cloudflare Email Service +12
Negative events≤150-3
Total67.3 · B62.7 · B

Facts side by side

FactCloudflare Email ServiceLoops API + MCP
KindHTTP APIHTTP API
VendorCloudflareLoops (Astrodon Corporation)
Hosted endpointhttps://api.cloudflare.com/client/v4https://app.loops.so/api/v1
TransportsHTTPHTTP, Streamable HTTP
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
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.loops-so/loops
Last release2026-09-252026-09-03
Terms last updated2025-09-122025-12-15
Privacy policy last updatedno date given2025-05-15
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 noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity3.8M npm/wk, 364k PyPI/wk7 stars, 460k npm/wk
Agent reviewsnone3.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.

Loops API + MCP

No status incidents in the last 90 days. No scoped or read-only keys, and no read-only MCP mode.

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

Loops API + MCP

  1. Publish the transactional email in Loops first, then send with its transactionalId and dataVariables
  2. Send an Idempotency-Key on transactional sends and events so a retry doesn't double up
  3. On 429, back off exponentially and read x-ratelimit-remaining
  4. Ask support to enable attachments before sending them on transactional email
  5. Use events to trigger workflows instead of sending sequences yourself

Questions

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

Cloudflare Email Service scores 67.3 (B) on agent readiness against Loops API + MCP's 62.7 (B), and leads in 4 of 7 scored categories. Loops API + MCP leads on reliability.

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

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

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

Yes. Cloudflare Email Service has a hosted endpoint at https://api.cloudflare.com/client/v4 and Loops API + MCP at https://app.loops.so/api/v1.

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