Compatible with every major AI agent and IDE
What is the Acelle Mail MCP Server?
Connect your Acelle Mail self-hosted or cloud account to any AI agent and simplify how you manage your mailing lists, subscriber data, and email campaigns through natural conversation.
What you can do
- List Management — List all your mailing lists, create new directories, and retrieve detailed configuration metadata.
- Subscriber Control — List and query subscribers for specific lists, and add new members programmatically via AI.
- Campaign Monitoring — List active and past email campaigns and retrieve detailed status and metadata for each outreach.
- Audience Oversight — Fetch list details and verify subscriber counts to manage your marketing reach.
- Automation Readiness — Manage your subscriber lifecycle and list organization directly from Claude, Cursor, or any MCP client.
How it works
- Subscribe to this server
- Enter your Acelle Mail API Token and Base URL
- Start managing your email marketing machine from your favorite AI assistant
Who is this for?
- Marketing Managers — quickly retrieve subscriber counts and campaign metadata via simple AI commands.
- Customer Success Teams — add new subscribers and verify list membership directly from the workspace.
- Email Outreach Specialists — monitor campaign statuses and manage audience segments via the AI assistant.
Built-in capabilities (7)
Add a subscriber
Create a new list
Get campaign details
Get list details
List all campaigns
List all mailing lists
List subscribers
Why CrewAI?
When paired with CrewAI, Acelle Mail becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Acelle Mail 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
Acelle Mail in CrewAI
Acelle Mail and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Acelle Mail 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 Acelle Mail in CrewAI
The Acelle Mail 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 7 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
Acelle Mail for CrewAI
Every tool call from CrewAI to the Acelle Mail MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the subscribers in a specific list via AI?
Yes! Use the list_acelle_subscribers tool and provide the List UID. Your agent will retrieve the directory of members associated with that mailing list.
How do I add a new subscriber to a list using the agent?
Use the add_acelle_subscriber action. Provide a JSON object with the subscriber's details, including 'EMAIL' and the target 'list_uid'. The agent will instantly register the new member.
Is it possible to check the status of my email campaigns via AI?
Absolutely. Use the list_acelle_campaigns query. The agent will retrieve all your active and past campaigns, allowing you to monitor their delivery status and performance metrics.
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 →
Deel
10 toolsManage global contracts, team members, invoices, payments, time-off, and expenses — global HR for AI agents.

Anthropic
10 toolsInteract with Claude models via the Anthropic Messages API — send prompts, manage batches, and monitor rate limits directly.

Moosend (Email Marketing & Automation)
10 toolsManage email marketing via Moosend — create campaigns, track mailing lists, and audit performance analytics.

Intercom
12 toolsConnect with customers through AI-powered chat, targeted messages, and product tours that drive engagement and reduce churn.
