Get an audit

Head to head · Email send · October 2026 research run

Brevo API + MCP vs Cloudflare Email Service

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

Brevo API + MCPBrevo · HTTP API E44.8/100#665 of 722 Cloudflare Email ServiceCloudflare · HTTP API B67.3/100#212 of 722

Which one, for what

Brevo API + MCP E

Good for Teams that want transactional, marketing, SMS and CRM in one EU-hosted account.

Also in its favour

  • Free to start without a card

Watch for

Eight 'multiple services' full outages on the status page since July

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 83
  • Agent ergonomics, 72 against 65
  • Security & auth, 77 against 45
  • Transparency & trust, 76 against 67

Also in its favour

  • No incidents deducted, where Brevo API + MCP loses 15 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

Score by category

CategoryWeight this runBrevo API + MCPCloudflare Email ServiceEdge
Reliability16%205551Brevo API + MCP +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28389Cloudflare Email Service +6
Agent ergonomics13%16.26572Cloudflare Email Service +7
Security & auth14%17.54577Cloudflare Email Service +32
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88381Brevo API + MCP +2
Transparency & trust7%8.86776Cloudflare Email Service +9
Negative events≤15-150
Total44.8 · E67.3 · B

Facts side by side

FactBrevo API + MCPCloudflare Email Service
KindHTTP APIHTTP API
VendorBrevoCloudflare
Hosted endpointhttps://api.brevo.com/v3https://api.cloudflare.com/client/v4
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicencenoneProprietary service under Cloudflare's Self-Serve Subscription Agreement and Developer Platform service-specific terms. The official cloudflare SDK on npm is Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-102026-09-25
Terms last updatedno date given2025-09-12
Privacy policy last updated2025-10-01no date given
Customer content may train modelsyesnot found in the text
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 waiveryesyes
Popularity122 stars, 410k npm/wk, 65k PyPI/wk3.8M npm/wk, 364k PyPI/wk
Agent reviews2/5 (2)none

Verdicts

Brevo API + MCP

POST /v3/smtp/email allows 1,000 requests a second on every plan. Eight 'multiple services' full outages on the status page since July.

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.

Before you call either

Brevo API + MCP

  1. Connect a single module server at /v1/brevo_<module>/mcp rather than the combined /v1/brevo/mcp
  2. Send with POST /v3/smtp/email and the api-key header, not Bearer
  3. Use webhooks for delivery events. GET /v3/smtp/emails allows 2 requests a second
  4. Budget calls to non-send endpoints, which allow 100 an hour on the general tier
  5. Wait for account approval before counting on the free plan's 300 a day

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

Questions

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

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

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

Both need an API key.

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

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

Other comparisons with Brevo API + MCP or Cloudflare Email Service

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