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 天免费 · 无需信用卡 · EU 托管
问 Brevo 任何事
通过 AnythingMCP 对 Brevo 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 BrevoClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Brevo。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
Brevo 指南
面向主流 AI 客户端的逐步设置。
配置 Brevo
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
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.