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 días gratis · sin tarjeta · hosting UE
Pregunta cualquier cosa a Brevo
Prueba un prompt real contra Brevo vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.
Instalar Brevo en CloudClaude es IA y puede equivocarse. Verifica siempre las respuestas.
Setup en 2 minutos
- 1Inicia trial gratuita en cloud.anythingmcp.com.
- 2Click en Brevo en el connector store. Pega las credenciales.
- 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Guías para Brevo
Setup paso a paso para los principales clientes AI.
Configurar Brevo
Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.
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.
Tu IA está a dos clicks de Brevo.
Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.