Bring Sms Marketing
to CrewAI
Learn how to connect Brevo to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Brevo MCP Server?
Connect your Brevo account to any AI agent and take full control of your marketing automation and transactional communication workflows through natural conversation.
What you can do
- Contact Orchestration — List and manage your contact database programmatically, retrieving detailed high-fidelity profiles and synchronizing custom attributes in real-time
- Campaign Intelligence — Create and monitor high-fidelity email marketing campaigns and retrieve detailed performance reports directly through your agent
- Transactional Messaging — Programmatically dispatch single transactional emails via Brevo SMTP to ensure perfectly coordinated customer notifications
- Audience Discovery — Access complete directories of contact lists and manage segmentations to maintain high-fidelity targeting for your digital outreach
- Operational Monitoring — Access account-level metadata, verified senders, and real-time SMTP delivery statistics for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key (v3) from your Brevo dashboard (SMTP & API settings)
3. Start managing your communication pipeline from Claude, Cursor, or any MCP client
No more manual toggling between campaign tables or digging through SMTP logs. Your AI acts as your dedicated CRM and marketing operations coordinator.
Who is this for?
- Digital Marketers — instantly retrieve campaign engagement metrics and update contact lists using natural language commands
- Growth Teams — automate the ingestion of new leads and monitor transactional email health without leaving your workspace
- Developers — integrate high-speed email marketing and SMTP features into custom workflows through simple AI queries
Built-in capabilities (11)
Create a new contact
Create an email campaign
Get Brevo account details
Get details for a specific contact
Get details for a specific list
Get SMTP delivery statistics
List contact lists
List Brevo contacts
List email campaigns
List approved senders
Send a transactional email
Why CrewAI?
When paired with CrewAI, Brevo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Brevo tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Brevo in CrewAI
Brevo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Brevo to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Brevo in CrewAI
The Brevo MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Brevo for CrewAI
Every tool call from CrewAI to the Brevo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Brevo API Key?
Log in to your account, navigate to Settings > SMTP & API, and generate a new v3 API Key.
Can I send transactional emails via AI?
Yes! The send_email tool allows your agent to dispatch single SMTP messages by providing sender and recipient details programmatically.
How do I check SMTP delivery statistics?
Use the get_smtp_statistics tool to retrieve high-fidelity reports on transactional email performance directly from the platform.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.