Maileon MCP Server for CrewAI 9 tools — connect in under 2 minutes
Connect your CrewAI agents to Maileon through Vinkius, pass the Edge URL in the `mcps` parameter and every Maileon tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Maileon Specialist",
goal="Help users interact with Maileon effectively",
backstory=(
"You are an expert at leveraging Maileon tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Maileon "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 9 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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
About Maileon MCP Server
Connect your Maileon account to any AI agent to automate your professional email marketing and audience management. This MCP server enables your agent to manage subscribers, control mailing lifecycles, and retrieve detailed performance statistics directly from natural language interfaces.
When paired with CrewAI, Maileon becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Maileon tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
What you can do
- Contact Management — List all subscribers, retrieve complete profiles by email, and manage opt-ins and opt-outs
- Mailing Control — Monitor your email campaigns (mailings), retrieve metadata, and trigger official dispatches when ready
- Real-time Reporting — Retrieve KPIs and statistics for individual mailings, including opens, clicks, and bounces
- Audience Hygiene — Monitor unsubscription events and permanently remove contacts to maintain list quality
- Data Ingestion — Create and update subscriber records programmatically to sync with your external CRMs
The Maileon MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Maileon to CrewAI via MCP
Follow these steps to integrate the Maileon MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 9 tools from Maileon
Why Use CrewAI with the Maileon MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Maileon through the Model Context Protocol.
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 `mcps` parameter 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
Maileon + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Maileon MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Maileon for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Maileon, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Maileon tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Maileon against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Maileon MCP Tools for CrewAI (9)
These 9 tools become available when you connect Maileon to CrewAI via MCP:
create_new_contact
Can trigger a Double Opt-In process if configured. Add or update a contact in the database
delete_account_contact
Remove a contact from the account
dispatch_email_mailing
The mailing must be in a ready state. Trigger the dispatch of a mailing
get_contact_by_email
Get details for a specific contact
get_mailing_details
Get details for a specific mailing
get_mailing_statistics
Get performance statistics for a mailing
list_account_contacts
Use optional params for filtering. List all contacts in the Maileon account
list_email_mailings
Use optional params to filter by state (e.g., "state=draft"). List all mailings (campaigns)
list_unsubscription_events
List recent unsubscription events
Example Prompts for Maileon in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Maileon immediately.
"List all active mailings in my Maileon account."
"Get the latest statistics for mailing ID '12345'."
"Add 'new-user@example.com' to my Maileon contacts."
Troubleshooting Maileon MCP Server with CrewAI
Common issues when connecting Maileon to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Maileon + CrewAI FAQ
Common questions about integrating Maileon MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Maileon with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Maileon to CrewAI
Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.
