Head to head · Sending email · October 2026 research run

Brevo API + MCP vs Loops API + MCP

Loops API + MCP scores 66.4 (B) on agent readiness against Brevo API + MCP's 44.4 (E), and leads in 3 of 7 scored categories. Brevo API + MCP leads on transparency & trust. Both do sending email.

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

Which one, for what

Brevo API + MCP E

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

Ahead on

  • Transparency & trust, 77 against 66

Watch for

'Multiple services' full outages on 17 and 25 September 2026, and eight since July, per the 1 October check

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 55
  • Schema & documentation, 82 against 58
  • Agent ergonomics, 70 against 65

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

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 +35

Brevo API + MCP 55

incident.io status page with 31 components (per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site) (20). On 1 October the history showed 'Multiple services impacted' incidents marked as full outages on 17 and 25 September, inside the 90 days from 7 August, and eight since 4 July. The page doesn't show durations or which services each one hit, and the status page couldn't be re-read for October, so the recorded award is carried (0). Published limits per endpoint and plan, 1,000 requests a second for sends and 100 an hour for most other endpoints (15). 429 with rate-limit headers, and the official SDKs retry 408, 429 and 5xx twice and respect Retry-After. No idempotency key for sends found (10). Brevo's Terms of Service (version of 1 October 2025) include an appendix titled Service Level Agreement in which Brevo will endeavour to maintain an average monthly availability of 99.8 per cent of the Software, with no credit or other remedy, and section 5.5 says the service comes as is and as available. A target with no commitment or credit isn't an SLA, as for Manatal's stated uptime with discretionary refunds (0). GA (10).

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.

Schema & documentation Loops API + MCP +24

Brevo API + MCP 58

The 1 October check read an OpenAPI file at developers.brevo.com/openapi.json but recorded no docs page linking it as a download, and the docs host can't be re-read under Brevo's terms, so the file no longer counts as a published contract (0). llms.txt and Markdown versions of the docs, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (10). Reference pages explain each endpoint, per the same check. The hosted MCP isn't open source, so we couldn't read its tool definitions (10). Typed request schemas in the same file, per the 1 October check. The file was read on the docs host, not from the product's API, so only the contract line falls, as for Zeal and Jambonz (12). Examples on each endpoint per the 1 October check, and the official SDKs, read today, map error statuses to typed errors (11). Dated API changelog and v3 in the path, per the 1 October check (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.

Transparency & trust Brevo API + MCP +11

Brevo API + MCP 77

Closed service with terms naming Sendinblue SAS. The official Node SDK repository carries no licence file (15). Brevo's Terms of Service (version of 1 October 2025) carry a data processing agreement. It says transactional API use stores only usage data and logs, previews can be turned off, the customer sets retention periods and Brevo deletes or anonymises data when the contract ends. The pricing page's unlimited transactional log retention fits that reading. No Brevo-set retention period (20 of 30). A dated deprecation for POST /contacts/batch (announced 12 May, removal 30 October), but no stated deprecation policy, and the 13 August CLI changes removed flags with no advance notice in the changelog (14). The 3 September Loyalty rename is deducted once, under negative events, not here. The data processing agreement lists sub-processors with company and server locations, among them OVH and Google Cloud in France and Belgium for hosting (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).

Agent ergonomics Loops API + MCP +5

Brevo API + MCP 65

27 per-module MCP servers let a client load only contacts, templates or another module rather than the combined server, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (18). limit, offset and sort on list endpoints (15). Errors map to typed classes in the SDKs. We didn't check for an error-code reference (12). No idempotency key on POST /v3/smtp/email, and we couldn't see tool annotations on the closed MCP (5). Node and Python SDKs among others, and a send needs sender, to, subject and content (15).

Loops API + MCP 70

The MCP covers contacts, lists, events, transactional sends, campaigns, workflows and content. We couldn't count its tools, and API responses are small (15). perPage and cursor pagination on lists (17). Errors come back with a message, and the SDK raises RateLimitExceededError with the limit attached. No error-code reference found (12). Idempotency-Key on events and transactional sends. We couldn't see MCP tool annotations (14). Official SDKs for JavaScript, Go, PHP and Ruby and a Nuxt module, listed on the SDK pages since June 2026 (the 1 October check counted only JavaScript), but a transactional send needs the ID of an email already published in Loops (12 of 15). 15 + 17 + 12 + 14 + 12 = 70.

Score by category

CategoryWeightBrevo API + MCPLoops API + MCPEdge
Reliability16%5590Loops API + MCP +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5882Loops API + MCP +24
Agent ergonomics13%6570Loops API + MCP +5
Security & auth14%5046Brevo API + MCP +4
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8383even
Transparency & trust7%7766Brevo API + MCP +11
Negative events≤15-15-3
TotalE 44.4/100B 66.4/100

Facts side by side

FactBrevo API + MCPLoops API + MCP
KindHTTP APIHTTP API
VendorBrevoLoops (Astrodon Corporation)
Hosted endpointhttps://api.brevo.com/v3https://app.loops.so/api/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.loops-so/loops
Last release2026-10-162026-10-20
Terms last updatedno date given2025-12-15
Privacy policy last updated2025-10-012025-05-15
Customer content may train modelsyesyes
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
Popularity122 stars7 stars, 460k npm/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Loops API + MCP higher.

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

Brevo API + MCP

Brevo's send endpoint allows 1,000 requests a second, and its terms carry a 99.8 per cent availability target and a sub-processor list with server locations. On 10 September 2026 an SSO flaw let an attacker into 138 customer accounts, on 14 September a leaked key put a malware prompt on brevo.com, and the MCP token has full account access.

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

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. Ask for an OAuth M2M app with only the scopes the task needs where the operator can set one up, rather than a full API key
  4. Use webhooks for delivery events. GET /v3/smtp/emails allows 2 requests a second
  5. Budget calls to non-send endpoints, which allow 100 an hour on the general tier

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, Brevo API + MCP or Loops API + MCP?

Loops API + MCP scores 66.4 (B) on agent readiness against Brevo API + MCP's 44.4 (E), and leads in 3 of 7 scored categories. Brevo API + MCP leads on transparency & trust.

Do Brevo API + MCP and Loops API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Brevo API + MCP and Loops API + MCP without installing anything?

Yes. Brevo API + MCP has a hosted endpoint at https://api.brevo.com/v3 and Loops API + MCP at https://app.loops.so/api/v1.

Other comparisons with Brevo API + MCP 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.