Integration walkthrough · Updated 2026-05-22

Brevo MCP + Claude: setup walkthrough and the 5 workflows that earn their install time

Brevo ships a hosted MCP server at https://mcp.brevo.com, API-key authenticated over remote HTTP. Documentation at help.brevo.com. The integration takes about 4 minutes to set up and is included on every paid Brevo tier starting at Starter ($9/mo). This walkthrough covers the setup, the 5 highest-leverage workflows, the daily-volume gotcha, and the operator hygiene that keeps the credential clean.

Want to try Brevo?

Brevo MCP is free on every paid tier — Starter starts at $9/mo

Wire it into Claude in 4 minutes. Email + SMS + transactional + contact management all from chat.

Start with Brevo →Affiliate link — StackSwap earns a commission if you sign up for Brevo. We only partner with tools we'd recommend anyway.

Step 1: Generate a Brevo API key

In Brevo: Settings → SMTP & API → API Keys → Create New API Key. Name it explicitly — "Claude integration (Nick)" or "AI - chat-driven sends" — so the activity log is readable later. Copy the token immediately; Brevo shows it once.

Operator hygiene note: Brevo's API permissions are workspace-wide rather than user- scoped, so treat the key as a high-trust credential. Don't paste it into shared agent configs or commit it to a repo; rotate on a regular cadence (monthly is reasonable for production use).

Step 2: Add Brevo MCP to Claude

Step 3: Verify the connection

Smoke test in chat: "Using the Brevo MCP, show me my contact lists." Claude should respond with your actual lists. If the call fails: (a) check the API key for paste truncation, (b) verify the endpoint URL is correct, (c) confirm the key has the permissions to read lists (most keys do by default). Fix in that order before deeper troubleshooting.

The 5 workflows that earn their install

1. Draft and send email campaigns from chat

"Draft a campaign to our 'Free trial — week 2' segment with three sections: a value recap, a customer success story, and a clear upgrade CTA. Schedule it for Tuesday 10 AM Eastern." Claude writes the copy, picks the segment, schedules the send. The confirmation gate in your MCP client is what stops it from firing without your approval.

2. Send transactional SMS for time-sensitive messages

"Send an SMS reminder to every customer with an appointment in the next 2 hours." Brevo's transactional SMS surface is reachable from MCP — useful for agent loops that need to fire time-sensitive notifications without going through email-specific workflow tooling.

3. Contact management at chat-speed

"Add jane@acme.example.com to our 'enterprise prospects' list with attributes company=Acme, tier=enterprise, source=referral." Replaces the manual list-management workflow. Useful inside agent loops that source contacts from elsewhere (Apollo MCP, scraped lists, form submissions) and need to push them to Brevo's marketing layer.

4. Template generation and A/B test prep

"Generate 3 subject-line variations for our upcoming product-launch email, optimized for opens. Save them as templates in Brevo so we can A/B test." The LLM writes; the MCP saves the templates; the next campaign-build picks from the variations.

5. Campaign performance summarization

"Pull performance data for our last 5 campaigns. Which had the highest engagement? Summarize what's different about the winning ones." Replaces the dashboard-walking session with a single chat exchange. The LLM has access to actual open/click/bounce data, not just operator memory.

The daily-volume gotcha — check quota before fan-out

Brevo's pricing is structured around daily email volume: Free 300/day, Starter 5,000/day, Business 20,000/day. The MCP doesn't enforce a soft warning before you hit the cap, so a fan-out send can exhaust the day's allocation. Three mitigations:

Where StackSwap MCP fits alongside Brevo MCP

Brevo MCP exposes your Brevo data. StackSwap MCP exposes the cross-vendor GTM catalog — ~400 tools with monthly costs, AI-readiness scores, overlap pairs. Load both into the same Claude session: "draft and send this campaign" (Brevo MCP) plus "what should our marketing-email stack look like at our scale" (StackSwap MCP).

Connect StackSwap MCP free →

Want to try Brevo?

Brevo MCP + Claude is the cheapest bundled marketing-email stack in 2026

$9/mo entry, 4-minute setup, email + SMS + transactional in one chat. The 5 workflows above earn the install on the first send.

Start with Brevo →Affiliate link — StackSwap earns a commission if you sign up for Brevo. We only partner with tools we'd recommend anyway.

FAQ

Generate an API key in Brevo (Settings → SMTP & API → API Keys → Create New API Key). In Claude Desktop or claude.ai: Settings → Connectors → Add custom MCP, paste the Brevo MCP endpoint (https://mcp.brevo.com) and your API key. In Claude Code: add the server to your workspace .mcp.json. Documentation lives at help.brevo.com/hc/en-us/articles/27978590646802. Smoke test in chat: 'List my Brevo lists' — if you see your contact lists, the connection is healthy.

API access is included on every paid Brevo plan starting at Starter ($9/mo for 5,000 emails/day). The Free plan (300 emails/day) includes API access too — sufficient for experimentation but quickly exhausted for production-scale workflows. Business at $18/mo (20K emails/day) and Enterprise tiers expand the daily-volume cap and unlock advanced features. The MCP layer is available across all paid tiers; the constraint is the daily email allocation, not MCP feature access.

Five workflows: (1) draft and send an email campaign from chat — Claude writes copy, picks segment, schedules send; (2) send transactional SMS for time-sensitive customer messages (order confirmations, password resets, appointment reminders); (3) manage contacts and companies — add to lists, update attributes, search records; (4) generate template variations and prep A/B tests; (5) pull campaign performance data and have Claude summarize what worked. The send surface is real — bulk campaigns and transactional messages both fire through MCP, so configure your client's confirmation UX before turning Claude loose on real recipient lists.

Two distinct limits to know. (1) API rate limits per key — typically generous for chat use, but agent loops fanning out across many contacts can hit them. Claude surfaces rate-limit errors in chat with the retry window. (2) Daily email volume cap — Free 300/day, Starter 5,000/day, Business 20,000/day. The MCP doesn't enforce a soft warning before you hit the cap, so a fan-out send can exhaust the day's allocation. Mitigation: query the account-details endpoint at the start of any send-heavy chat session to check remaining quota.

Yes — though Brevo's permissions are workspace-wide rather than fine-grained, you should still create a dedicated key for Claude use, named explicitly ('Claude integration — Nick'). Don't share the same key across production scripts and chat-driven workflows; rotation and revocation get simpler when each use has its own key. The activity log shows actions under the issuing key, so isolated keys = isolated audit trails. For production-grade use, consider IP allowlisting if your Brevo tier supports it.

Bulk sends are where the write surface earns its name and where the blast radius lives. Three mitigations: (1) configure your MCP client's confirmation UX — Claude Desktop tends to be most explicit about confirming each write op; (2) prompt-engineer a confirmation gate ('before any send touching more than 50 recipients, ask the user to confirm'); (3) use Brevo's Test mode and Test segments — build agent loops against test recipient lists first, promote to production once the behavior is calibrated. For revenue-critical or compliance-sensitive sends, keep human-in-the-loop review regardless of LLM confidence.

Zapier routes through a workflow runner — Claude calls Zapier, Zapier calls Brevo. Adds latency, a failure point, and a separate cost line ($19.99-$199/mo on the volumes that matter). Direct Brevo MCP is structurally simpler: Claude → Brevo, one hop. For chat-driven campaign drafting and contact management, native MCP wins. Zapier still earns its place for event-driven workflows ('when a Brevo contact subscribes, post to Slack and create a HubSpot contact'). Different problem, different tool. Most operator stacks use MCP for chat-driven work and Zapier for event-driven destination plumbing.

Yes to all three. Claude Desktop and claude.ai both support custom MCP connectors — Settings → Connectors → Add custom MCP, paste endpoint + API key. Claude Code reads MCP server config from your workspace .mcp.json. Same MCP underneath; the auth flow differs only in how you paste the credential into the surface. Confirmation UX differs by client — Claude Desktop is most explicit per-operation; test bulk-send flows on the surface you'll actually use before production.

Related reading

Canonical URL: https://stackswap.ai/brevo-mcp-claude-integration. Disclosure: StackSwap is a Brevo affiliate.