How to Use the Mailsac MCP in CrewAI

Q: How do I configure the Mailsac server for CrewAI?

Pass the server URL directly into the mcps array when defining your Agent. CrewAI handles the connection automatically.

Q: Can a CrewAI agent read plain text emails from Mailsac?

Yes. The getplaintextbody tool strips out the HTML so your agent only reads the raw text content.

Q: How do I restrict which Mailsac tools my CrewAI agent can use?

Import MCPServerHTTP from the CrewAI MCP module. Use the toolfilter argument to expose only the exact endpoints that specific agent needs.

Q: Can CrewAI search my entire Mailsac account for a specific email?

Yes, via the searchaccountmessages tool. Your agent can pass subject lines or sender addresses to locate the exact message.

Arm your CrewAI agents with Mailsac disposable addresses to autonomously test email routing and parse inbound messages.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mailsac MCP to CrewAI

Create your Vinkius account to connect Mailsac to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Mailsac with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Delegate Inbox Setup

You can assign a specific CrewAI agent to manage your email infrastructure. This setup agent uses the Mailsac MCP Server to check `list_custom_domains` and pick a valid routing target. It then calls `reserve_new_address` to lock down a testing inbox. The agent passes that new address directly into the crew's shared memory for the next agent to use.

Monitor and Extract Data

The next agent in your sequence acts as the monitor. Its entire job is to watch the new inbox by polling `list_inbox_messages`. When a message drops, the agent grabs the content via `get_html_message_body`. It extracts the necessary verification tokens or links, completely ignoring the layout markup.

Tear Down Test Artifacts

A separate moderator agent handles the teardown phase. You don't want test artifacts clogging up your Mailsac dashboard. The moderator triggers `delete_inbox_message` to wipe the sensitive contents first. Then it fires `release_reserved_address` to return the inbox to the available pool.

Setup guide

Set up Mailsac MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Mailsac tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Mailsac Analyst",
    goal="Access and analyze Mailsac data via MCP.",
    backstory="Expert analyst with direct Mailsac access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Mailsac transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Mailsac Analyst",
        goal="Access and analyze Mailsac data via MCP.",
        backstory="Expert analyst with direct Mailsac access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Mailsac transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mailsac. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Mailsac now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Mailsac MCP in CrewAI

Pass the server URL directly into the `mcps` array when defining your Agent. CrewAI handles the connection automatically.

Yes. The `get_plain_text_body` tool strips out the HTML so your agent only reads the raw text content.

Import `MCPServerHTTP` from the CrewAI MCP module. Use the `tool_filter` argument to expose only the exact endpoints that specific agent needs.

Yes, via the `search_account_messages` tool. Your agent can pass subject lines or sender addresses to locate the exact message.

CrewAI pulls the exact message body into the agent's context window. The LLM reads it to extract your verification data. Ensure your tests only send synthetic data to avoid leaking PII to your model provider.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript