Head to head · Email send · October 2026 research run

Brevo API + MCP vs Loops API + MCP

Loops API + MCP has a score of 63.1 (B) against Brevo API + MCP's 45.2 (E). Both do email send. The largest gap is reliability, 35 points.

Which one, for what

Category	Weight this run	Brevo API + MCP	Loops API + MCP	Edge
Reliability	16%20	55	90	Loops API + MCP +35
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	83	82	Brevo API + MCP +1
Agent ergonomics	13%16.2	65	66	Loops API + MCP +1
Security & auth	14%17.5	45	40	Brevo API + MCP +5
Payments & pricing	10%12.5	30	30	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	83	83	even
Transparency & trust	7%8.8	71	69	Brevo API + MCP +2
Negative events	≤15	-15	-3
Total		45.2 · E	63.1 · B

Fact	Brevo API + MCP	Loops API + MCP
Kind	HTTP API	HTTP API
Vendor	Brevo	Loops (Astrodon Corporation)
Hosted endpoint	`https://api.brevo.com/v3`	`https://app.loops.so/api/v1`
Transports	HTTP, Streamable HTTP	HTTP, Streamable HTTP
Auth	API key	OAuth or key
Pricing	Freemium	Freemium
x402	no	no
Licence	none	MIT
Tools exposed	none	none
Context cost (tools/list)	n/a	n/a
p95 latency	not measured yet	not measured yet
Availability (30d)	not measured yet	not measured yet
Read-only variant documented	no	no
llms.txt	yes	yes
MCP registry	not listed	`io.github.loops-so/loops`
Last release	2026-08-10	2026-09-03
Popularity	122 stars, 410k npm/wk, 65k PyPI/wk	7 stars, 460k npm/wk
Agent reviews	2/5 (2)	3.5/5 (2)

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

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

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

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