Brevo — can an agent use it?
Brevo ships an official MCP server with 193 auto-generated tools and a mature REST API covering campaigns, contacts, CRM, and transactional messaging. The default 250 req/hour rate limit is tight for agent workflows — Professional tier unlocks real throughput. Terms prohibit generic bots but the official MCP surface makes programmatic access a supported path.
FIND & RETRIEVE · 6.8
ACT & TRANSACT · 6.9
TRUST & DURABILITY · 6.8
FIND & RETRIEVE6.8/10Can an agent get correct information?
Machine-readable surface7/10
Server-rendered HTML with 821 words of real content visible to non-JS crawlers. Valid JSON-LD (Organization, Offer, FAQPage, WebSite). Multi-language sitemaps referenced in robots.txt. No llms.txt. No AI-specific robots.txt policy — crawlers inherit the permissive wildcard rules. No structured markdown negotiation. source
Information retrieval quality6.5/10
Pricing page renders with real content showing Free/Starter/Standard/Professional/Enterprise tiers, but actual prices are loaded dynamically (the excerpt shows tier names and feature lists but not dollar amounts). Rate limits are documented at developers.brevo.com/docs/api-limits with exact numbers per tier. Feature comparison is detailed. Enterprise pricing requires 'Talk to sales'. source
Documentation for machines7/10
Developer portal at developers.brevo.com provides API reference, guides, SDKs, and code recipes. The 193-tool MCP server was auto-generated from the OpenAPI spec, confirming the spec is comprehensive. Webhooks documented (inbound parse webhooks). The builder's fetch returned 303 redirects on doc pages, suggesting regional gating or JS-heavy rendering — a friction point for agents trying to read the docs programmatically. source
ACT & TRANSACT6.9/10Can an agent do the job?
Action coverage7.5/10
API covers all core marketing actions: campaign creation and sending, contact management, transactional email/SMS via SMTP relay and API, CRM deal management, automation workflows, and conversation handling. The MCP server exposes 193 tools covering campaigns, contacts, sales pipeline, CRM, loyalty, and transactional sends. Webhooks for inbound parsing. The main gap is that some advanced automation rule configuration may be UI-only. source
Agent protocol support8/10
Official Brevo MCP server, launched early access October 2025, with March 2026 security update (Bearer token auth, rate limiting, simplified maintenance). 193 tools auto-generated from OpenAPI spec. Hosted/remote — no local install required. Supports Claude, ChatGPT, Cursor, and any MCP-compatible client. Covers the service's core actions (send campaigns, manage contacts, CRM operations). Not in the official MCP registry at github.com/modelcontextprotocol/servers, but it is first-party and maintained by Brevo. source
Access & auth friction7/10
API key authentication — self-serve, generated from the Brevo dashboard. MCP server uses Bearer token in Authorization header (upgraded from URL-based token in March 2026). No OAuth 2.0 flow documented for third-party agent delegation. Keys appear to be account-scoped without granular permission scoping. Self-serve credentials obtainable in minutes on all plans including free. source
Agent payment capabilityN/A
Brevo is a subscription service. Customers pay Brevo a monthly fee, not a per-transaction amount that an agent would mediate. No agent payment protocol (ACP, AP2, MPP, x402) applies. source
Cost & rate fairness5/10
Default rate limit of 250 requests/hour across all plans is restrictive for agent workflows. Professional tier unlocks meaningful throughput: 2,000 RPS for email sends, 200 RPH for other endpoints. Enterprise tier extends further. Free tier includes 300 emails/day and API access. HTTP 429 responses with rate limit headers for monitoring. The jump from 250 RPH to Professional-tier limits is steep — agent traffic on lower tiers will hit walls quickly. source
TRUST & DURABILITY6.8/10Will it still work next quarter?
Permission & ToS stance6/10
Terms of use explicitly prohibit 'any engine, software, tool, agent or other device or mechanism (including browsers, spiders, robots, avatars, or intelligent agents)' for unauthorized access. However, Brevo simultaneously ships an official MCP server designed for AI agent use, creating a contradiction: the terms ban generic bots while the product actively supports agent workflows via sanctioned channels. The conservative read is that API/MCP access under valid credentials is permitted, but the blanket language leaves room for selective enforcement. Anti-spam policy adds further constraints on automated messaging. source
Reliability & continuity7.5/10
Public status page at status.brevo.com monitors 35+ components across 10 service categories (Marketing, Transactional, Automations, CRM, Conversations, Commerce, Data Platform, Integrations). Currently fully operational. 600,000+ customers indicates institutional stability. Formerly Sendinblue (rebranded 2023), with continuous platform evolution. No specific SLA percentage published in evidence, and no documented API deprecation notice periods. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- brevo.com — home (accessed 2026-09-15)
- brevo.com/pricing — pricing (accessed 2026-09-15)
- brevo.com/legal/termsofuse — terms of use (accessed 2026-09-15)
- brevo.com/robots.txt — robots (accessed 2026-09-15)
- brevo.com/sitemap.xml — sitemap (accessed 2026-09-15)
- status.brevo.com — status page (accessed 2026-09-15)
- developers.brevo.com — developer portal (accessed 2026-09-15)
- developers.brevo.com/docs/api-limits — API rate limits (accessed 2026-09-15)
- developers.brevo.com/docs/mcp-protocol — MCP documentation (accessed 2026-09-15)
- brevo.com/releases/new-release-brevos-mcp-server — MCP server release announcement (accessed 2026-09-15)