What format is required for the instance host?

Provide the full hostname without the 'https://' prefix, for example: `box.yourdomain.com`.

Can I add multiple forwarding targets to an alias?

Yes, when using the `create_or_update_alias` tool, provide a comma-separated list of emails in the `forwards_to` field.

Does this work with 2FA enabled accounts?

The current API implementation uses Basic Auth. If 2FA is enabled on your admin account, you may need to use an API key or a dedicated admin user without 2FA for the integration.

Mail-in-a-Box MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Mail-in-a-Box
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Mail-in-a-Box through Vinkius, pass the Edge URL in the `mcps` parameter and every Mail-in-a-Box 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="Mail-in-a-Box Specialist",
    goal="Help users interact with Mail-in-a-Box effectively",
    backstory=(
        "You are an expert at leveraging Mail-in-a-Box 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 Mail-in-a-Box "
        "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)

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 Mail-in-a-Box MCP Server

Connect your Mail-in-a-Box instance to any AI agent to automate your private email server management. This MCP server enables your agent to manage mailboxes, configure forwarding aliases, and monitor system health and diagnostics directly from natural language interfaces.

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

User Administration — List all mail users, create new mailboxes, and update passwords programmatically
Alias Management — Create, update, and remove email forwarding addresses and group aliases
System Monitoring — Retrieve real-time health status, diagnostic checks, and configuration metadata for your server
Domain Oversight — List all hosted mail domains and subdomains configured on your instance
Access Control — Manage administrative privileges and account settings for your email users

The Mail-in-a-Box 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 Mail-in-a-Box to CrewAI via MCP

Follow these steps to integrate the Mail-in-a-Box 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 Mail-in-a-Box

Why Use CrewAI with the Mail-in-a-Box MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Mail-in-a-Box 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

Mail-in-a-Box + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Mail-in-a-Box MCP Server delivers measurable value.

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

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

Mail-in-a-Box MCP Tools for CrewAI (9)

These 9 tools become available when you connect Mail-in-a-Box to CrewAI via MCP:

create_mail_user

Requires a full email address and a password. Add a new mail user (mailbox)

create_or_update_alias

forwards_to should be a comma-separated list of emails. Add or update a mail alias

delete_mail_alias

Remove a mail alias

delete_mail_user

Remove a mail user

get_system_status

Check the status of the Mail-in-a-Box system

list_mail_aliases

List all mail aliases and forwarders

list_mail_domains

List all mail domains hosted on the server

list_mail_users

List all mail users on the server

update_user_password

Change the password for a mail user

Example Prompts for Mail-in-a-Box in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Mail-in-a-Box immediately.

"List all mail users on my server."

"Create a new mail user 'support@example.com' with password 'MySecret123!'."

"How is the health status of my Mail-in-a-Box server?"

Troubleshooting Mail-in-a-Box MCP Server with CrewAI

Common issues when connecting Mail-in-a-Box 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.

Mail-in-a-Box + CrewAI FAQ

Common questions about integrating Mail-in-a-Box 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.