Head to head · Sending email · October 2026 research run

Cloudflare Email Service vs Loops API + MCP

Cloudflare Email Service and Loops API + MCP score within a point of each other on agent readiness, 67 (B) and 66.4 (B). Loops API + MCP leads on reliability. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Cloudflare Email Service B

Best 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
  • Security & auth, 79 against 46
  • Transparency & trust, 77 against 66

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

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

Ahead on

  • Reliability, 90 against 53

Also in its favour

  • Free to start without a card

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Loops API + MCP +37

Cloudflare Email Service 53

Graded on the hosted Email Sending REST API with the hosted lines. www.cloudflarestatus.com is a Statuspage with Email Sending and Email Routing as separate components, both operational on 1 November (20). The incidents feed read on 8 October held 50 incidents from 19 September to 8 October 2026, and the feed read on 1 November holds 50 from 16 to 31 October. Neither names either email component. The labelled majors since 16 October are regional or limited to one product (network connectivity in North America on 23 October, customers behind an external vendor firewall on 27 October, R2 and Durable Objects on 21 October), so they read as partial. The history page loads by script, so 3 August to 18 September and 9 to 15 October went unread. 12 of 30 (10 before), as cloudflare-r2, cloudflare-mcp and cloudflare-workers-ai read the same page with an unread stretch on 1 November. 1,200 API requests per five minutes per token and 200 a second per IP, 50 recipients and 25 MiB per message. The daily sending quota and the send rate limit still have no published number (12 of 15). The send endpoint documents 429 with code 10004, the Cloudflare API returns retry-after and Ratelimit headers, and the SDKs back off. No idempotency key for sends (9 of 15). No SLA found, and the agreement gives no commitment for beta services (0). Email Sending is still marked Beta on the docs home page (updated 15 October), although the OpenAPI send operation is tagged generally-available. We scored from the docs (0). 20 + 12 + 12 + 9 + 0 + 0 = 53.

Loops API + MCP 90

Statuspage at status.loops.so with components for sending, transactional, API, SMTP relay and webhooks (20). One incident in the 90 days to 2 November, "Delay in email metric processing" on 11 September (about 90 minutes, metrics slow to appear in the app, none lost), which doesn't touch the API or sending, so the record reads as clean (30). 10 requests a second per team, and 60 a minute for the content endpoints (15). 429 with x-ratelimit headers and advice to retry with exponential backoff, and an Idempotency-Key header on event and transactional sends (15). No SLA found on the pricing page (0). GA (10). 20 + 30 + 15 + 15 + 0 + 10 = 90.

Security & auth Cloudflare Email Service +33

Cloudflare Email Service 79

Cloudflare API tokens are revocable and scoped by permission, with separate send and read permissions, an optional expiry and an IP address filter. A send token covers every onboarded domain on the account, and the OpenAPI operation also accepts the legacy global API key (27 of 30). A read-only permission exists, and a Workers binding can be limited to named sender or destination addresses. Accounts without a sending domain can reach only verified addresses. No approval step for sends or deletes (14 of 20). Sending returns no untrusted content, but Email Routing hands inbound mail to Worker code and the docs suggest email as a way to drive agents, with no prompt-injection guidance found (6 of 15). Account audit logs record domain and suppression changes for 18 months, and each send is visible in the activity log and GraphQL datasets for about 30 days (14 of 15). security.txt, re-read on 1 November, names HackerOne and a disclosure policy and has no Expires field. Cloudflare's ISO certifications page, read on 1 November, says it is certified to ISO 27001 (since 2019, now 27001:2022), ISO 27018 and ISO 27701, with a scope of the Cloudflare global cloud platform, which doesn't name Email Service. 2 held back for the missing Expires field, which RFC 9116 requires, as cloudflare-r2, cloudflare-workers-ai and cloudflare-sandbox-sdk read the same evidence (18 of 20, 16 before, when certifications went unread). 27 + 14 + 6 + 14 + 18 = 79.

Loops API + MCP 46

Bearer API keys created and revoked in settings. The hosted MCP uses browser OAuth with Client ID Metadata Documents and no documented scopes (22). No read-only or send-only keys and no read-only MCP mode found (0). No inbound mail, so tools return only account data (10). No audit log found (0). A security reporting page (updated 19 October 2026) takes reports at security@loops.so, acknowledges within a few days and pays for reports scored CVSS v4 4 or higher, and a compliance page links the SOC 2 trust centre at trust.oneleet.com/loops and a DPA. No security.txt (404 on 2 November) and no published advisories. Below customer-io (16, which adds HIPAA and penetration tests) and sendgrid (15, which adds ISO 27001) (14 of 20). 22 + 0 + 10 + 0 + 14 = 46.

Transparency & trust Cloudflare Email Service +11

Cloudflare Email Service 77

Closed service under the Self-Serve Subscription Agreement and service-specific terms with an Email Service section updated on 28 September 2026, unchanged on 1 November. The SDKs are Apache-2.0 (18 of 30). The privacy policy of 4 November 2025 (re-read on 1 November) makes Cloudflare a processor of customer content and a DPA is published. The docs give about seven days for message previews, 31 days for send events and 18 months for audit logs. The terms say message content may be scanned by automated tools. No retention period for message content in transit or queued was found (20 of 30). No deprecation policy found. The agreement lets Cloudflare change or end a service without notice and remove a beta service at any time (4 of 20). The sub-processor list, last updated 1 October 2025, names Google and Oracle for the Developer Platform with locations. Where email is processed isn't stated (15 of 20).

Loops API + MCP 66

Closed service with published terms and an MIT JavaScript SDK (20). The privacy policy (updated 15 May 2025) says customer contact and message data is returned or deleted within 30 days of termination and account data within 12 months, links a DPA, and says aggregated or anonymised data is used for machine learning in the product (22). Dated deprecations, such as List custom fields on 14 January 2025, but a breaking change on 17 September shipped with same-day notice (12). No subprocessor list. The policy names Stripe, Google Analytics, Segment and GitHub and says data goes to the US (8).

Schema & documentation Cloudflare Email Service +7

Cloudflare Email Service 89

Cloudflare's public OpenAPI 3.0.3 file, re-read on 1 November, still has 29 operations under /email/sending and 46 under /email/routing (25). llms.txt for the product and a Markdown copy of every docs page (10). Operation descriptions state the purpose and the guides say when to pick REST, the binding or SMTP, with little on when not to call an operation (14 of 20). Address fields are typed as a string, a named object or an array, attachments use a discriminator on disposition, and error messages are enums. Custom headers are a free map (12 of 15). Request samples in curl, TypeScript, Python, Go and Terraform, a table of 15 REST error codes (10207, sending paused for the account, added since 8 October) and 20 binding codes. The guide's sample response omits message_id and suppressed_recipients, and its error table omits the 409 the OpenAPI file documents (13 of 15). Version in the path (/client/v4) and a dated product changelog with RSS (15).

Loops API + MCP 82

OpenAPI 3.1 in YAML and JSON at app.loops.so, version 1.22.8 on 2 November with 48 paths and 72 operations (25). llms.txt, Markdown copies of every docs page and agent skills for coding agents (10). The reference explains each endpoint. The hosted MCP isn't open source, so we couldn't read its tool definitions (10). Typed inputs in the spec, with ranges such as perPage between 10 and 50 (12). Examples for the API, SDKs and CLI on each examples page, and the spec declares 400, 404, 409, 422 and 429 answers, but the API intro doesn't document the error format (10). Dated API changelog with entries to 20 October, and a versioned spec (15). 25 + 10 + 10 + 12 + 10 + 15 = 82.

Score by category

CategoryWeightCloudflare Email ServiceLoops API + MCPEdge
Reliability16%5390Loops API + MCP +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8982Cloudflare Email Service +7
Agent ergonomics13%7270Cloudflare Email Service +2
Security & auth14%7946Cloudflare Email Service +33
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8183Loops API + MCP +2
Transparency & trust7%7766Cloudflare Email Service +11
Negative events≤15-3-3
TotalB 67/100B 66.4/100

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-10-20
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 reviews3.3/5 (4)3.5/5 (2)

The panel on both

The one reviewer who reviewed both, Sprint, rates Loops API + MCP higher, the other way from the total score.

ReviewerCloudflare Email ServiceLoops API + MCP
SprintLatency and reliability tester 2/5 Beta service with no send limit number and no SLA 4/5 No incidents in 90 days, and a retry key on sends

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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

Event and transactional sends take an Idempotency-Key, the status page shows no incident touching the API in 90 days, and official SDKs cover four languages. Keys can't be scoped or limited to reads, and the hosted MCP has no read-only 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 25 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 and Loops API + MCP score within a point of each other on agent readiness, 67 (B) and 66.4 (B). 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.