Compatible with every major AI agent and IDE
What is the MailerLite MCP Server?
Connect your MailerLite account to any AI agent and manage email marketing through natural conversation.
What you can do
- Campaign Management — Create, schedule, and track email campaigns
- Subscriber Management — Add, segment, and manage subscriber groups
- Automation Workflows — Browse and monitor automated email sequences
- Analytics — Track open rates, click rates, and subscriber growth
- Form & Landing Pages — Access signup forms and landing page data
How it works
- Subscribe to this server
- Enter your MailerLite API Key and API version
- Start managing email from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Marketers — run email campaigns with advanced analytics
- Small Businesses — manage subscriber lists and automations
- Creators — grow audiences with landing pages and forms
Built-in capabilities (10)
Use this to organize and segment your audience. Create a new subscriber group
Get details for a specific subscriber
Useful for monitoring marketing activity. List email campaigns
Essential for identifying which fields can be mapped during subscriber upserts. List all custom subscriber fields
List all signup forms
Groups are used to organize subscribers for targeted mailings. List all subscriber groups
Useful for identifying high-engagement subsets of your audience. List all subscriber segments
Includes email addresses, statuses, and basic engagement metadata. List all email subscribers
List active account webhooks
Requires the email address and supports optional first/last name fields. Create or update a subscriber
Why CrewAI?
When paired with CrewAI, MailerLite becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call MailerLite 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
MailerLite in CrewAI
MailerLite and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect MailerLite 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 MailerLite in CrewAI
The MailerLite 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 10 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
MailerLite for CrewAI
Every tool call from CrewAI to the MailerLite MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create campaigns and track performance?
Yes. Create and schedule campaigns, send to groups or segments, and track opens, clicks, bounces, and conversions in real time.
Does MailerLite require an API version parameter?
Yes. MailerLite requires an API Key and API Version (v1 or v2) for configuration. Bearer auth against api.mailerlite.com/api/v2.
Can I manage automation workflows?
Yes. Browse active automations, monitor trigger rates, and view email sequence performance.
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 →
Casting42
8 toolsManage talent databases and casting projects via Casting42 — track profiles, media, and custom attributes directly from any AI agent.

Baremetrics
12 toolsSaaS financial analytics — audit MRR, churn, LTV, and customer subscriptions via AI.

Zoho Inventory
9 toolsManage inventory items, sales orders, and stock levels via the Zoho Inventory API.

LearnUpon
9 toolsManage users, courses, and enrollments via the LearnUpon LMS API.
