Access, auth, and limits
Connecting is straightforward: generate an MCP API key from Account > SMTP & API inside your Brevo dashboard, then point your client at https://mcp.brevo.com/v1/brevo/mcp with that key as a Bearer token. Because it's hosted by Brevo, there's nothing to install or run locally on your side.
For a desktop client like Claude, you'd add the hosted endpoint as a remote MCP server with the Bearer token in the auth config. The research doesn't confirm a specific Claude Code one-liner or a list of officially tested clients, so treat setup as standard remote-MCP wiring and verify the connection handshakes before relying on it.
Where it works and what to build
A concrete workflow: ask your agent to "find every contact who opened last week's newsletter but didn't click, add them to a re-engagement list, and draft a follow-up email." With the MCP server connected, the agent can query contacts, manipulate lists, and stage the send through Brevo's tools instead of you hopping between screens.
The research lists no verified clients, so I can't tell you which editors or desktop apps Brevo has confirmed working. Since it's a standard hosted MCP endpoint with Bearer auth, any MCP-compatible client (Claude Desktop, Cursor, Claude Code) should in principle connect, but test your specific setup rather than assuming it.
How to connect Brevo MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"brevo": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.brevo.com/v1/brevo/mcp
// Claude Code (one-liner): claude mcp add brevo <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.brevo.com/v1/brevo/mcp.
Does Brevo MCP cost extra?
Brevo ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Brevo plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Brevo also publishes a REST API
Brevo publishes an API, but per-tier gating wasn't extracted automatically.
See Brevo API pageWhat you can do with Brevo from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Brevo data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Brevo account
- Multi-account workflows without context-switching the Brevo UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Brevo data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Brevo safe
Limits and gotchas
- Official MCP server — published by Brevo themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Brevo API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Wiring Brevo into an agent makes sense if you're already a Brevo customer and want Claude or Cursor to handle contact updates, email triggers, and campaign lookups without a homegrown integration. It's an official hosted server with clean Bearer auth, which is genuinely more than most competitors offer. The unknowns, no confirmed tool list and no tested-client roster, keep it from a top mark. A solid 7 out of 10.
Weak agent-fit without official tooling. Brevo has a community MCP server and documented public API, but lacks OpenAPI specs, SDKs, and native integrations with Claude or ChatGPT. The missing structured outputs and webhook support make it difficult to build reliable agent workflows that require real-time triggers or predictable JSON responses.
Scored by Joonas (TMB).
Brevo MCP & API FAQ
Is the Brevo MCP server official?+
Can I use the Brevo MCP with Cursor or Codex?+
Does Brevo have a public API?+
Sources
- Brevo official site: https://www.brevo.com/
- MCP server page: https://mcp.brevo.com/v1/brevo/mcp
- API docs: https://developers.brevo.com/
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.