Brevo
Drive Brevo (formerly Sendinblue) — transactional email/SMS, marketing campaigns, contacts and lists — from any AI agent. 14 tools, api-key header auth, EU-based deliverability.
7-day free trial · No credit card · EU-hosted
Ask Brevo anything
Try a real prompt against Brevo via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.
Install Brevo on CloudClaude is AI and can make mistakes. Please double-check responses.
Setup in 2 minutes
- 1Start a free trial on cloud.anythingmcp.com.
- 2Click Brevo in the connector store. Paste credentials when prompted.
- 3Mint an MCP API key and point your AI client at the generated MCP URL.
Guides for Brevo
Step-by-step setup for the most popular AI clients.
Setting up Brevo
From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.
This connector uses the Brevo REST API v3 (formerly known as Sendinblue API).
Setup:
- Sign in to https://app.brevo.com → top-right avatar → SMTP & API → API Keys → Generate a new API key.
- Name it ('AnythingMCP'). It's prefixed
xkeysib-. SetBREVO_API_KEY.
Authentication: custom header api-key: ${BREVO_API_KEY} (lowercase header name — Brevo-specific). The adapter sets it via API_KEY profile.
Verified sender: just like SendGrid, you must verify your sending domain or sender email before transactional email actually delivers (otherwise it lands in spam or is rejected). Brevo → Senders & IP → Senders → Add a sender OR domain authentication via SPF/DKIM.
Transactional vs Marketing: brevo_send_transactional_email is for app-triggered 1-to-1 sends (receipts, password resets). brevo_create_email_campaign + brevo_send_email_campaign_now are for newsletter-style sends to a list. Pricing tiers are split per channel.
Contact lists vs folders: contacts can belong to multiple lists. Lists can be organized into folders (for UI tidiness; folders have no behavioral meaning). Use brevo_list_contact_lists to discover list IDs.
Custom attributes: each contact has attributes (FIRSTNAME, LASTNAME, plus any you define). Set them in brevo_create_contact via the attributes object: {FIRSTNAME:'Jane', LANGUAGE:'fr'}.
Pagination: most list endpoints use limit (max 50 typically, 100 for some) + offset.
SMS sending: also via the API. brevo_send_transactional_sms requires a verified sender name (≤11 chars, alphanumeric) AND the recipient phone in international format with + prefix.
Webhooks out of scope (configured in UI for delivery to your hosted endpoint).
Rate limits: ~400 req/sec for transactional email, lower for management endpoints. On 429, Retry-After is set.
Out of scope here: WhatsApp Business via Brevo (use the dedicated WhatsApp Business connector), CRM/deals (separate Brevo product, not on the same API surface), conversations, automation workflows, attribute creation.
Your AI is two clicks away from Brevo.
Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.