Does my AI agent need a preexisting Gmail or Outlook account to use this?

No. AgentMail is entirely standalone. You can use your agent to programmatically provision brand new, unique email addresses in seconds, completely independent of legacy email providers.

Can my agent download files that users send to its email address?

Yes. When scanning threads in the inbox, your agent will detect any attached files. It can then use the dedicated attachments tool to retrieve and analyze the contents of the file before drafting a reply.

Is it possible to manage multiple outreach campaigns at the same time?

Absolutely. Your agent can create and manage multiple inboxes simultaneously. It can list all active boxes, read unread threads for each, and contextualize its replies based on the specific campaign inbox.

AgentMail MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: AgentMail
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to AgentMail through Vinkius, pass the Edge URL in the `mcps` parameter and every AgentMail tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="AgentMail Specialist",
    goal="Help users interact with AgentMail effectively",
    backstory=(
        "You are an expert at leveraging AgentMail 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 AgentMail "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 AgentMail MCP Server

Connect AgentMail to your AI agent and unlock a programmable email client. Stop relying on complex integrations and grant your agent its own functional inbox to communicate with the world.

When paired with CrewAI, AgentMail becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AgentMail 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

Inboxes — Create, list, and delete custom email addresses on the fly for your agent
Threads — Scan active conversations and read full historical threads natively
Messages — Send new emails, reply contextually to specific threads, and forward messages
Attachments — Extract and process files attached to incoming emails automatically

The AgentMail MCP Server exposes 11 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 AgentMail to CrewAI via MCP

Follow these steps to integrate the AgentMail 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 11 tools from AgentMail

Why Use CrewAI with the AgentMail MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AgentMail 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

AgentMail + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AgentMail MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AgentMail 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 AgentMail, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AgentMail 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 AgentMail against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AgentMail MCP Tools for CrewAI (11)

These 11 tools become available when you connect AgentMail to CrewAI via MCP:

create_inbox

You can optionally link it to a custom domain. Create a new email inbox for an agent

delete_inbox

Warning: this deletes all emails in it. Delete a specific inbox by ID

forward_message

You can optionally add text to the forwarded message. Forward an existing email message

get_attachment

Attachments might be encoded in base64. Ensure you parse or read it correctly. Download or read a specific attachment from a message

get_inbox

Get details of a specific inbox by ID

get_thread

Requires a thread_id. Read all messages inside a specific conversation thread

list_inboxes

An inbox is required to send or receive emails. Returns an array of inboxes with their IDs, email addresses, and names. List all inboxes assigned to the AgentMail API Key

list_threads

Returns a list of thread objects including subject lines and recent message previews. The agent needs an inbox_id first. List conversation threads inside an inbox

reply_to_message

The thread will be preserved. Reply to an existing email message/thread

send_message

Requires the sender inbox_id, which you can get from list_inboxes. Send a brand new email message

update_message

Update an existing message metadata (like marking it as read)

Example Prompts for AgentMail in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AgentMail immediately.

"Create a new inbox for our support team."

"Check all my unread threads in the main inbox today."

"Reply to the client thanking them and attach the pricing PDF."

Troubleshooting AgentMail MCP Server with CrewAI

Common issues when connecting AgentMail to CrewAI through the Vinkius, and how to resolve them.

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.

AgentMail + CrewAI FAQ

Common questions about integrating AgentMail MCP Server with CrewAI.

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.