Brevo API + MCP (2026): official MCP server, v3 REST, 7 SDKs

Brevo runs one REST API at v3 on api.brevo.com, covering transactional email, contacts, campaigns, CRM objects, SMS, domains and webhooks from a single key. It is also one of very few ESPs with a first-party MCP server — a remote endpoint at mcp.brevo.com, live since October 14, 2025, exposing 27 modules. The trap is credential sprawl: Brevo issues an SMTP key, a v3 API key and an MCP token, and none substitutes for another.

At a glance

MCP integration in 2026

Most platforms in this category still have no first-party Model Context Protocol surface, leaving buyers to choose between community wrappers and generic HTTP tool-calling. Brevo is the exception.

Available MCP servers

The first three are Brevo’s own documentation surfaces for the same hosted server; the last two are third-party.

Brevo API essentials

One versioned base path for everything: no split marketing and transactional hosts, no per-region endpoint, no request signing — a plain header carries the key.

The model is broad rather than deep. /v3/smtp/email is the API-side twin of the relay covered on the SMTP settings tab — same account, same domain authentication, same 20 MB ceiling. Around it sit contacts and lists, campaigns, CRM objects, senders and domains, webhooks, inbound parse and Enterprise sub-accounts. Brevo prices on email volume rather than stored contacts, so contact endpoints are cheap commercially but expensive to use quickly.

Authentication methods

API key header

The primary method. Create a key under Account › SMTP & API › API Keys and send it in the api-key header on every call — no bearer prefix, no HMAC, no timestamp. Validate with GET /v3/account: a health check that costs no send.

OAuth 2.0 for marketplace apps

Publishing into the Brevo App Marketplace uses OAuth 2.0 rather than a static key, managed with the first-party Brevo CLI (brevo app create, upload, scaffold). The CLI reached v2.0.0 on July 2, 2026 with breaking changes from v1.1.1.

MCP API token

The MCP server rejects your v3 API key. It needs a separate MCP token, created in the same Account › SMTP & API area and sent as Authorization: Bearer <token>. Brevo shows it once at creation, with no retrieval screen after.

Rate limits

Limits are per endpoint, in requests per second, across three tiers: General, Advanced (Professional and Enterprise) and Extended (Enterprise only). The spread between endpoints matters far more than between tiers.

Hourly, that is 3,600,000 sends on General — a number almost nobody reaches. Contacts, at 36,000 per hour, is 100x tighter and is the real ceiling: any sync looping contact by contact returns 429 long before sending is stressed. Use the asynchronous bulk import instead — submit the batch, take the process id, poll GET /v3/processes/{processId}. Account quotas apply independently of rate: 200 contact attributes, 300 lists (600 on Professional), 40 outbound and 20 inbound webhooks.

Official SDKs

Seven clients plus a CLI live in the getbrevo organisation, all generated from the same v3 specification. Method coverage is consistent; maintenance cadence is not.

Notable community SDKs

Brevo publishes no list of third-party clients, and seven official languages leave little room for one — community effort went into MCP wrappers instead. What registries still carry are Sendinblue-era packages under the old sib-api-v3-sdk naming: not forks, but the previous generation of the official clients.

Endpoints reference

The fifteen resources below cover what most integrations touch; full schemas sit in the Brevo API reference.

Webhooks come in three types, all created through POST /v3/webhooks: transactional (Sent, Delivered, Opened, Clicked, Soft and Hard Bounce, Invalid Email, Deferred, Complaint, Unsubscribed, Blocked, Error), marketing for campaign events, and inbound carrying inboundEmailProcessed. Inbound parse is a full product, not a raw MIME dump: it splits the reply from the quoted thread and signature into ExtractedMarkdownMessage and ExtractedMarkdownSignature.

Code examples

Verify an API key

Run this first: a 200 confirms the credential type and the plan tier governing your limits.

curl -s https://api.brevo.com/v3/account -H "api-key: YOUR_V3_API_KEY"

# 200 -> email, companyName, plan[] and relay status.
# 401 -> wrong credential type (SMTP key or MCP token), or revoked.
# 429 -> over the tier limit for this endpoint.

Send a transactional email (Python)

The brevo-python v5.x shape. On v4 the import path and client construction differ.

# pip install brevo-python  (v5.x)
from brevo import Brevo
from brevo.transactional_emails import (
    SendTransacEmailRequestSender,
    SendTransacEmailRequestToItem,
)

client = Brevo(api_key="YOUR_API_KEY")

client.transactional_emails.send_transac_email(
    sender=SendTransacEmailRequestSender(
        email="hello@yourdomain.com", name="Alex from Brevo"),
    to=[SendTransacEmailRequestToItem(
        email="johndoe@example.com", name="John Doe")],
    subject="Hello from Brevo!",
    html_content="<p>Tracking code: {{params.trackingCode}}</p>",
    params={"trackingCode": "JD01460000300002350000"},
)

# v5 replaced the legacy sib_api_v3_sdk / SibApiV3Sdk client.
# On v4? Pin it: pip install 'brevo-python>=4,<5'

Send a transactional email (Node.js)

// npm install @getbrevo/brevo
import { BrevoClient } from '@getbrevo/brevo';

const brevo = new BrevoClient({ apiKey: process.env.BREVO_API_KEY });

const result = await brevo.transactionalEmails.sendTransacEmail({
  sender: { name: 'Alex from Brevo', email: 'hello@yourdomain.com' },
  to: [{ email: 'johndoe@example.com', name: 'John Doe' }],
  subject: 'Hello',
  textContent: 'Hello world!',
});

// Replaces the old SibApiV3Sdk.TransactionalEmailsApi pattern.

Connect an MCP client

Clients with HTTP transport take the URL and Bearer header directly; stdio-only ones bridge via mcp-remote. Scope to one module unless you need all 27.

{
  "mcpServers": {
    "brevo-contacts": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.brevo.com/v1/brevo_contacts/mcp",
        "--header", "Authorization: Bearer YOUR_MCP_API_TOKEN"
      ]
    }
  }
}

# All 27 modules:  https://mcp.brevo.com/v1/brevo/mcp
# Per module:      https://mcp.brevo.com/v1/brevo_{module}/mcp

Common gotchas

Deprecations and changelog

• August 14, 2026 — New endpoint returning the records associated with a single object record, with filtering and pagination.
• August 13, 2026 — CLI workflow overhaul: brevo app upload replaces brevo app update and shows a diff before pushing, and brevo app scaffold recovers a project folder.
• July 20, 2026 — Transactional Email gained contactPixelTrackingConsent for per-contact open-tracking consent. Email Campaigns gained UTM customisation for utm_campaign, utm_content and utm_term.
• July 2, 2026 — Brevo CLI v2.0.0 released with breaking changes from v1.1.1. The Deals API gained server-side filters for owner, stage and pipeline.
• October 14, 2025 — Official MCP server launched in early access, now documented at https://mcp.brevo.com/v1/brevo/mcp with 27 modules.

Running API changes appear in the developer changelog, product news at brevo.com/releases. Nothing on v3 is marked for deprecation — the breaking changes of the last two years were client-side rewrites, not endpoint removals: a fair stability signal against SendGrid or Mailjet.

Frequently asked questions