Brevo MCP Server
Connect Brevo to your AI agents with the Brevo MCP server.
Updated
What is Brevo MCP?
The Brevo MCP server is a Model Context Protocol server that connects Brevo to AI agents and assistants as a set of tools. With it connected, an agent can work with Brevo (email marketing & crm — campaigns, contacts, transactional email, automation) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Brevo tools become available to the model.
Connect the Brevo MCP server
Connect Brevo MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Brevo MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Brevo tool to confirm the connection is live.
Connect Brevo MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Brevo
Provide the Brevo MCP server URL or command and complete authentication.
- 3
Test
Reference Brevo from chat to confirm Cursor can reach the tools.
Using Brevo MCP with Gamut
On Gamut, the Brevo MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Brevo and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Brevo MCP server?
It is a Model Context Protocol server that exposes Brevo to AI agents as tools so they can work with it (email marketing & crm — campaigns, contacts, transactional email, automation).
How do I connect the Brevo MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Brevo MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.
Can I use Brevo MCP with Gamut?
Yes — Gamut supports the Brevo MCP server, so your agents can use it as a tool in automated, triggered workflows.