MCP · Email and SMS marketing · Brevo
Brevo MCP Server
Manage Brevo contacts, campaigns and transactional email from an AI host through Brevo's hosted server or narrower single-module servers.
The main server can do almost anything. The combined server includes account, user and webhook management. Use the narrowest module server for each task.
Understand the tool
What it does.
Brevo's hosted MCP server exposes Brevo's marketing and transactional features to AI hosts. A main endpoint combines 27 modules, and Brevo also documents individual servers such as contacts-only, which give the agent a smaller tool set.
Why use it?
Use it to look up contacts, review campaign results or draft emails. Prefer an individual module server for the task at hand, so the agent cannot reach unrelated features such as account users or webhooks.
A useful fit for
- Contact lookups and list hygiene
- Campaign result reviews
- Drafting transactional or campaign email
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Clean up a contact list
A small business wants to find duplicate or bounced contacts.
- Connect the contacts-only server.
- Find contacts with hard bounces or duplicates.
- Export a list for a person to review.
Intended outputA review list, with deletions left to a person.
Use case 02
Review last month's campaigns
An owner wants a quick results summary.
- List campaigns from last month.
- Pull opens and clicks.
- Summarize the best and worst.
Intended outputA short summary with numbers to confirm in Brevo.
A concrete starting point
Illustrative prompt: bounced contacts
The contacts-only server limits the agent to one module; the prompt also excludes writes.
Using Brevo's contacts-only MCP server, find contacts in the list I name that hard-bounced in the last 30 days. Show email, bounce date and list name. Do not delete, unsubscribe or edit any contact.What this can change
Contact data enters the AI host and its model provider.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- A Brevo account.
- An MCP token created under Account > SMTP & API > API Keys with the MCP option checked.
- An MCP client that supports remote servers with a bearer header.
- Authentication
- A Brevo MCP token sent as a bearer header.
- Can read
- Contacts, lists, campaigns, transactional logs and other modules enabled on the chosen server
- Can write or change
- Contacts, campaigns, email sends and, on the main server, account users and webhooks
- Network and data flow
- Brevo services
- AI host/model provider
- Approval and control
- The main server's single advertised scope is all. Use an individual module server to narrow access.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Remote MCP clients with bearer headers
- Main server or 27 individual module servers
- Bridge configuration documented for stdio-only clients
Costs and account requirements
Brevo plan pricing and sending limits apply.
Current pricing or plan information ↗Hosted service terms
No public source license for Brevo's hosted implementation is asserted. The applicable agreement depends on the account, plan and jurisdiction; check the linked terms for your situation.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
The main server can do almost anything
The combined server includes account, user and webhook management. Use the narrowest module server for each task.
Sends reach real recipients
Email and SMS tools send to real people. Require confirmation before any send.
Where it may fall short
- Only the main endpoint's authentication challenge and metadata were checked.
- Individual module servers were not probed.
Observed behavior · 2026-10-18
Runtime and security findings.
The main endpoint rejected credential-free initialization and pointed to public OAuth metadata with a single scope, all.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation · medium severity under stated conditions
One scope for everything
The main server's metadata advertised a single scope named all.
In practice: Connect an individual module server instead of the main one for routine tasks.
Version, environment and fixture
- Version or deployment
- Remote deployment version not disclosed by the observed responses
- Tested target
- https://mcp.brevo.com/v1/brevo/mcp
- Artifact identity
- HTTPS certificate verification enabled. Public resource-metadata body SHA-256: de937ba6d952e2afbc2fe448d006634b62c1367c8ae893aa25060a15a7937f81. This fingerprints the observed metadata, not the deployed server implementation.
- Environment and fixture
- Debian Linux x86_64 (kernel 6.12) evaluation box; Python 3.13.5 urllib; OpenSSL 3.5.7.
- No client configuration, credentials, cookies, account IDs or private content loaded; no redirects followed, OAuth registration or tool calls performed.
- Observed 2026-10-19T05:52:06.358620+00:00 through 2026-10-19T05:52:06.964620+00:00 UTC.
- One request per listed check; 20-second timeout and 64-KiB response cap. Raw timestamps are UTC; review date October 18, 2026.
Checks and results
2 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationMet expectation
- Method
POST https://mcp.brevo.com/v1/brevo/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream. Content-Type: application/json; MCP-Protocol-Version: 2025-03-26; body: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"IonBin-account-free-evaluation","version":"1.0.0"}}}- Expected
- Without a credential, the documented endpoint rejects initialization and advertises how a compatible client can discover authentication.
- Observed
- HTTP 401 at 2026-10-19T05:52:06.358620+00:00. WWW-Authenticate: Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.brevo.com/.well-known/oauth-protected-resource/v1/brevo/mcp". Body: {"error":"invalid_token","error_description":"Authentication required"}
Public authentication discoveryMet expectation
- Method
GET https://mcp.brevo.com/.well-known/oauth-protected-resource/v1/brevo/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream.- Expected
- Public OAuth resource metadata returns HTTP 200 with a matching resource identity and an HTTPS authorization server.
- Observed
- HTTP 200 at 2026-10-19T05:52:06.964620+00:00; Content-Type: application/json. Resource: https://mcp.brevo.com/v1/brevo/mcp. 1 advertised scope: all. Authorization server: https://mcp.brevo.com/oauth. Bearer methods: header.
Practical caveats
- The documented setup uses a static MCP token; store it like a password.
- Contact data is personal data.
What this evaluation does not establish
- MCP-token access, module scoping and account permissions.
- Contact edits, campaign and transactional sends, tool lists and prompt-injection resistance.
- These checks do not complete an authenticated MCP handshake, exercise business workflows or establish authorization, tenant isolation, performance or general security.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
Well-documented, with a useful option to narrow tools by module. The combined server's broad 'all' scope ranks it below more tightly scoped servers.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Main endpoint and authentication discovery
- Documented module servers
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official Brevo MCP guide ↗developers.brevo.com
- Brevo terms of use ↗www.brevo.com
- Brevo pricing ↗www.brevo.com