How to Use the Mailshake MCP in CrewAI

Q: Can CrewAI agents handle Mailshake prospect lists?

Yes, they can iterate through listcampaignrecipients to clean your data. They perform this work in the background without needing your constant input.

Deploy a crew of autonomous agents to manage your Mailshake outreach. Scale your sales operations with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mailshake MCP to CrewAI

Create your Vinkius account to connect Mailshake 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 Mailshake with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative outreach in CrewAI

Assign a researcher agent to `list_campaign_recipients` while a strategist agent uses `get_campaign_details` to optimize your next move. They work together to refine your targeting. You build the crew, and the MCP Server provides the raw data. The agents share context to make smarter decisions about who to contact.

Autonomous lead monitoring in CrewAI

Set a monitor agent to watch for new entries using `list_campaign_leads` and pull history with `get_lead_history`. It detects patterns that a human would miss. This setup identifies high-intent leads instantly. The crew flags these for your sales team, ensuring no opportunity goes unnoticed.

Automated message auditing in CrewAI

Use `list_outreach_messages` to analyze the tone of your current sequences. Your agents audit the performance and suggest updates to improve your response rates. It turns your outreach into a self-improving system. The agents run these checks on a schedule, keeping your messaging sharp and relevant.

Setup guide

Set up Mailshake 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 Mailshake tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Mailshake 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="Mailshake Analyst",
        goal="Access and analyze Mailshake data via MCP.",
        backstory="Expert analyst with direct Mailshake access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Mailshake 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 Mailshake. 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 Mailshake 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 Mailshake MCP in CrewAI

Pass the Vinkius URL into your agent's MCP configuration. The agents will then have direct access to every Mailshake tool you enable.

Yes, they can iterate through `list_campaign_recipients` to clean your data. They perform this work in the background without needing your constant input.

The agent reports the error back to the crew manager. You can set up a secondary agent to handle the escalation or retry the operation.

Your Mailshake credentials stay behind the Vinkius proxy. The agents only get the permissions you explicitly grant them via the tool filter.

Data is processed in-memory during the agent task. No logs of your prospect history are saved, and the connection is strictly point-to-point.

Use it with your favorite AI tools

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

OpenAI Agents SDK sdk-python