How to Use the Mailshake MCP in LangChain

Q: How do I connect the Mailshake MCP Server to LangChain?

Install langchain-mcp-adapters and use the MultiServerMCPClient. Pass the HTTP transport URL to the client and call gettools() to bind them to your agent.

Q: Can LangChain agents read Mailshake message content?

Yes. The agent calls getmessagecontent to pull the exact email copy. You can then pipe that text into an LLM to evaluate the pitch or draft a personalized reply.

Q: Why did my LangChain agent fail to add prospects to Mailshake?

The addprospectstocampaign tool requires a specific JSON schema for recipient details. Check your LangSmith traces to see if the agent passed malformed data or missed a required field.

Q: How does LangChain handle Mailshake API rate limits?

You build retry logic directly into your chain. If listcampaignleads hits a limit, the agent catches the 429 error and waits before trying again.

Build multi-step cold outreach pipelines by connecting Mailshake to your LangChain agents via this MCP Server.

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 LangChain

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chain Mailshake MCP Server Tools

The `list_outreach_campaigns` tool feeds directly into your LangChain ReAct agents. Your agent reads the active campaigns, parses the IDs, and decides which one needs immediate attention. You don't write glue code for this. The agent takes the campaign ID and passes it right into `get_campaign_details` to pull the active stats. LangSmith logs the exact latency and token usage for both API calls.

Automate Prospect Ingestion

The `add_prospects_to_campaign` tool accepts JSON arrays of recipient data straight from previous steps in your chain. If your agent scrapes a website or queries a database, it formats the output and pushes the leads into Mailshake automatically. Combine this with `list_campaign_recipients`. Your agent checks who is already in the sequence before adding new targets. This prevents duplicate outreach and keeps your domain reputation intact.

Trigger Campaign Controls

The `pause_outreach_campaign` tool halts active sending when your agent detects a problem. If an upstream sentiment analysis node flags too many negative replies, the chain triggers the pause function immediately. You verify the fallout using `get_lead_history` and `list_outreach_messages`. The agent pulls the exact email copy and reply logs, formats a summary, and drops it in your Slack channel for manual review.

Setup guide

Set up Mailshake MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Mailshake tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "mailshake-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Mailshake transactions"
    })
    print(result["messages"][-1].content)

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 LangChain

Install `langchain-mcp-adapters` and use the `MultiServerMCPClient`. Pass the HTTP transport URL to the client and call `get_tools()` to bind them to your agent.

Yes. The agent calls `get_message_content` to pull the exact email copy. You can then pipe that text into an LLM to evaluate the pitch or draft a personalized reply.

The `add_prospects_to_campaign` tool requires a specific JSON schema for recipient details. Check your LangSmith traces to see if the agent passed malformed data or missed a required field.

You build retry logic directly into your chain. If `list_campaign_leads` hits a limit, the agent catches the 429 error and waits before trying again.

The MCP protocol keeps your lead history and message content confined to your local environment. Vinkius handles the authentication endpoint, but the actual prospect emails and reply logs flow directly from the API to your local agent memory. Nothing gets stored on our infrastructure.

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