Compatible with every major AI agent and IDE
What is the Mailjet MCP Server?
Connect your Mailjet account to any AI agent and manage email operations through natural conversation.
What you can do
- Email Sending — Send transactional and marketing emails at scale
- Contact Management — Manage contact lists with properties and segmentation
- Template Management — Browse, create, and manage email templates
- Delivery Analytics — Track opens, clicks, bounces, and spam reports
- Campaign Management — Create and monitor email campaigns
- Statistics — Access detailed sending statistics and trends
How it works
- Subscribe to this server
- Enter your Mailjet API Key and Secret Key
- Start managing email from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — integrate email sending with rich APIs
- Marketers — manage campaigns and contact lists
- Operations — monitor deliverability and sender reputation
Built-in capabilities (12)
Add email to contacts
Check account stats
) for a specific campaign ID. Check campaign stats
Get template content
List audience contacts
List contact lists
List saved templates
Check sending domains
List past campaigns
Send transactional email
Send using template
Add contact to list
Why CrewAI?
When paired with CrewAI, Mailjet becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mailjet 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
Mailjet in CrewAI
Mailjet and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Mailjet 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 | 4,000+ 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 Mailjet in CrewAI
The Mailjet 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 12 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
Mailjet for CrewAI
Every tool call from CrewAI to the Mailjet MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send both transactional and marketing emails?
Yes. Mailjet supports both transactional (triggered) and marketing (campaign) emails through the same API.
Does Mailjet require two API keys?
Yes. Mailjet uses API Key and Secret Key pair with Basic Auth against api.mailjet.com/v3.
Can I manage contact lists and segments?
Yes. Create and manage contact lists, set contact properties, and build segments with dynamic conditions.
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.
Explore More MCP Servers
View all →
Dropbox
8 toolsManage cloud storage via Dropbox — list folders, search files, handle shared links, and monitor space usage directly from any AI agent.

DISQO
10 toolsEquip your AI agent to manage consumer insight projects, track audiences, and monitor behavioral metrics via the DISQO API.

Automate visual discovery via Pinterest — manage boards, create pins, and track performance directly with AI.

QuickBooks Online
10 toolsConnect QuickBooks to AI — query invoices, manage customers, run financial reports, and automate accounting workflows.
