Brevo MCP server
Brevo in any MCP client, through Memtro: Brevo does not publish this server. Memtro's Brevo connector reads Brevo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read-only email and SMS marketing: contacts with list memberships, lists with counts, email and SMS campaigns with delivery/open/click statistics, and transactional email reports.
Reads
brevo_contactsLook up one Brevo contact by email or id (with list memberships, blacklist flags, attributes and 90-day engagement)…brevo_listsContact lists with subscriber counts (total, unique, blacklisted) and folder ids.brevo_email_campaignsEmail campaigns with sent/delivered counts, unique opens and clicks (with rates), bounces, unsubscribes and complaints, newest first…brevo_sms_campaignsSMS campaigns with sent/delivered/bounce/unsubscribe/reply counts, newest first.brevo_transactional_statsAggregated transactional (SMTP/API) email statistics for a date range or the last N days (max 90): requests, delivered, opens, clicks, bounces…
Connect it
First connect Brevo on Dashboard → Connections, then add Memtro to your client once. The Brevo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
One command registers the server; the tools are then available in every session.
claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
--header "Authorization: Bearer sk-memtro-..."Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Brevo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › How did last Thursday's product update email perform?
- › Which lists is dana@northwind.io subscribed to?
- › How many transactional emails bounced this month?
- › Compare open rates across the last five newsletters
Questions
- Is this an official Brevo MCP server?
- No. It is Memtro's MCP server with Memtro's Brevo connector behind it: the connector reads Brevo through its API with the credentials you connect on Dashboard → Connections, and Brevo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Brevo?
- Not yet. Today every Brevo tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.