Brevo

Name: Brevo MCP Server
Availability: InStock
Author: Brevo

Sales & CRM21 tools

Analyse email and SMS campaign performance, explore contacts and segments, and create campaign and template drafts from Claude in plain language. Brevo caps the connector below the send line and states so in the directory listing itself — a claim that survives testing against the tool list.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Brevo via MCP

https://mcp.brevo.com/v1/anthropic/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Brevo Tools & Capabilities (21)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

No campaign send or schedule, by design. No tool sends or schedules email or SMS. Brevo states this in the directory description, in a capability matrix, and in a dedicated FAQ answer, and the absent sendNow and status-change endpoints corroborate it.
One tool does send mail. templates_send_test_template sends a transactional template test.
Scheduling in the create-campaign body is unverified. The REST endpoint beneath the tool accepts scheduledAt and sendAtBestTime. We did not authenticate, so we could not read the tool's inputSchema to confirm those are not exposed. Brevo says they are not.
The contact export returns direct-identifier personal data inline. Email addresses, contact ids, list membership, consent and blocklist state, and an open attributes object whose contents your own schema defines. It enters the model's context; there is no file and no URL.
The export is capped at 500 records per call with a default of 50 and offset paging. That slows bulk egress; it does not prevent an agent from looping.
No scope separates a contact lookup from a list export. Both sit under contacts:read.
No delete capability at all. Zero deletion verbs among the 21 names, against 38 delete operations in Brevo's REST API. The connector cannot action an erasure request.
Contacts, lists, segments and attributes are read-only. No contact can be created, edited or moved between lists, and no contacts:write scope exists.
The connector ignores per-user Brevo permissions. Brevo states access is granted by the MCP key regardless of the individual's role, calls it a known limitation, and advises sharing access only with trusted users.
One Brevo account per Claude account. Multiple accounts require custom connectors on the wildcard-scoped API-key surface.
Two Brevo MCP servers exist and are easy to confuse. The 27-module API-key server includes CRM deals, user management, WhatsApp, and SMS and WhatsApp modules Brevo describes as sending. Guidance written for that server does not describe this connector.
Features and rate limits vary by plan. Brevo states this in its plan-availability notice but publishes no MCP-specific rate-limit figures we could find in its help centre.
No MCP-specific data-protection documentation. Brevo's EU residency statement covers its own hosting; its GDPR page does not mention MCP, AI assistants or Anthropic, and no sub-processor listing naming an AI provider was found.
Your contact data reaches Anthropic. Brevo states its terms give way to Anthropic's once data is shared, and that Brevo data is not used to train the models, with limited exceptions.
Brevo warns about hallucination on your own data. Its FAQ states Claude can produce inaccurate results, and advises checking outputs, asking for references to specific Brevo data, and not relying on AI alone for critical decisions.
We could not verify tool behaviour ourselves. The endpoint returns 401 anonymously, so no inputSchema and no readOnlyHint or destructiveHint annotations were readable. Every capability claim here comes from Brevo's documentation, its published OpenAPI specification, or Anthropic's listing — not from annotations we inspected.
Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own check.

Frequently asked questions

Can the Brevo MCP server send or schedule an email campaign?

No. Brevo caps the connector at draft creation and states so in three places: the directory listing text, a capability matrix in its help centre, and a dedicated FAQ answer. The tool list corroborates it — the REST endpoints that send a campaign or flip its status have no matching tool. One narrow exception exists: a transactional template test-send tool.

What does the Brevo contact export tool return and where does it go?

It returns contact records inline in the chat response, not a download link. Brevo's OpenAPI specification for the endpoint beneath it caps a page at 500 contacts and defaults to 50, with offset paging. Each record carries the email address, contact id, custom attributes, list memberships, timestamps and email, SMS and WhatsApp blocklist flags.

Which OAuth scopes does the Brevo MCP server request?

Eight named scopes, verified live on 2026-08-19: account read, contacts read, and separate read and write scopes for email campaigns, SMS campaigns and transactional email. That is a genuine permission vocabulary rather than a wildcard. Note the asymmetry — contacts are read-only with no write scope offered, and no scope distinguishes reading a contact from exporting a whole list.

Can the Brevo MCP connector delete contacts or campaigns?

No. None of the 21 tools carries a deletion verb, and Brevo states the connector has no delete capability. This is a deliberate narrowing, not an oversight: Brevo's REST API publishes 38 delete operations across 207 paths, including one that erases a contact outright. The connector exposes none of them.

Does Brevo store contact data in the EU, and does it reach Anthropic?

Brevo documents EU-only storage: OVH in France and Germany, plus Google Cloud in Belgium. That covers Brevo's own hosting. Data you pull through the connector reaches Anthropic separately — Brevo states Anthropic's terms then apply and that Brevo data is not used to train the models. Brevo publishes no MCP-specific residency statement.

Do you need a paid Brevo plan to use the MCP connector?

No. Brevo states the connector is available on all plans, including free, though it notes that available features and API rate limits vary by plan. A free Claude account also works, with Brevo recommending a paid one for a better experience. Connecting requires only that you can sign in and authorise the OAuth prompt.

How many tools does the Brevo MCP server have?

The Anthropic directory lists 21 for the Claude connector endpoint. Brevo separately documents a different MCP server at another path, authenticated by API key, spanning 27 modules including CRM deals, user management and WhatsApp campaigns. The directory connector is the narrower of the two surfaces, and the two should not be confused.

Sources

Brevo connector for Claude — https://help.brevo.com/hc/en-us/articles/35030032898194-Brevo-connector-for-Claude-Use-your-Brevo-data-and-campaigns-in-Claude (fetched 2026-08-19 via the Zendesk Help Center JSON API at /api/v2/help_center/en-us/articles/35030032898194.json; article last updated 2026-07-01. The read/create/send capability matrix, the never-send-or-schedule-or-delete statement, all-plans availability, setup and disconnect steps, the seven documented example prompts, the one-account-per-Claude-account limit, the per-user-permissions known limitation, the no-delete-capability answer, the Anthropic-terms and no-training statements, and the hallucination guidance) · retrieved 2026-08-19
What is Model Context Protocol (MCP)? — https://help.brevo.com/hc/en-us/articles/35030003354130-What-is-Model-Context-Protocol-MCP (fetched 2026-08-19; article last updated 2026-05-11. The separate API-key MCP server, its MCP-key generation flow, the 27-module main server and the per-module endpoint table including the SMS and WhatsApp modules described as sending) · retrieved 2026-08-19
Data storage location — https://help.brevo.com/hc/en-us/articles/360001005510-Data-storage-location (fetched 2026-08-19; article last updated 2026-08-05. EU-only hosting, OVH in France and Germany, Google Cloud in Belgium, triple replication across two geographies, weekly encrypted backups) · retrieved 2026-08-19
Brevo API definition (OpenAPI 3.0) — https://api.brevo.com/v3/swagger_definition_v3.yml (fetched 2026-08-19; 207 paths and 291 operations, of which 38 are HTTP DELETE. The getContactsFromList response schema and its 500/50 paging caps, the getContactDetails field enumeration, the createEmailCampaign and SMS create bodies including scheduledAt and sendAtBestTime, the sendTestTemplate 50-per-day and empty-recipient behaviour, and the absent-from-MCP sendNow, campaign status and exportRecipients operations) · retrieved 2026-08-19
Brevo GDPR — https://www.brevo.com/company/gdpr/ (fetched 2026-08-19; data-subject rights and customer guidance. Contains no mention of MCP, AI assistants or Anthropic, and closes by recommending qualified legal counsel) · retrieved 2026-08-19
Brevo security — https://www.brevo.com/security/ (fetched 2026-08-19; no residency, sub-processor or MCP statement found in served content) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an initialize call to https://mcp.brevo.com/v1/anthropic/mcp returns HTTP 401 with a JSON body and a full RFC 9728 www-authenticate challenge naming the resource-metadata URL. No tool was called and no authentication was attempted · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptors — 2026-08-19. Path-append form at mcp.brevo.com/.well-known/oauth-protected-resource/v1/anthropic/mcp returns 200 with eight named scopes; the root form returns a JSON 404 and the path-insert form a plain-text 404. Per-client variants diffed: /v1/openai/mcp returns the identical scope set against its own authorisation server, /v1/brevo/mcp and the brevo_* module paths return ["all"] against a shared one, and /v1/foo/mcp returns a structured JSON 404 · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — mcp.brevo.com/.well-known/oauth-authorization-server/v1/anthropic/oauth (fetched 2026-08-19; issuer, authorize, token and register endpoints all under the per-client path, authorization_code and refresh_token grants, PKCE S256 only, token_endpoint_auth_methods_supported: ["none"], and the same eight scopes). The root form describes the wildcard surface. OpenID Connect discovery returns a JSON 404 · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/01a9fda6-bd91-4f02-af05-d8e4c3f4f556 (snapshot 2026-08-16; 21 tool names, permissions of "Read and write", the free-text description stating the never-send and never-delete cap, no prompt names, partner tier, Sales & Marketing category) · retrieved 2026-08-16
Documentation-discovery notes, 2026-08-19: help.brevo.com/robots.txt serves the stock Zendesk ruleset with no Content-Signal header of any kind and no MCP-relevant disallow; help.brevo.com/llms.txt and help.brevo.com/sitemap.xml both 404 into an HTML shell. www.brevo.com/robots.txt also carries no Content-Signal axes and indexes six per-language sitemaps. Help-centre articles were read through the documented Zendesk JSON API rather than the HTML pages · retrieved 2026-08-19