Marketing Automation
Mailshake MCP connector
The Mailshake connector brings your campaigns, recipients, leads and reply activity to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about outreach and act on it inside their own Mailshake access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Mailshake to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Mailshake once
-
Open Connections, choose Add connection, and pick Mailshake.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Mailshake API key. One person generates a token in Mailshake and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Mailshake to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Mailshake to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Mailshake to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Mailshake to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Mailshake through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
See who replied before the standup
Ask which recipients replied to a campaign overnight, read the replies together, and decide who gets a call first.
-
Outbound
Add a new list to a campaign
Hand over a batch of names and email addresses and have them added to the right Mailshake campaign, then confirm they all went in.
-
Sales
Pause a recipient who booked a meeting
When a prospect books time, pause or unsubscribe them so the next follow-up never lands in their inbox.
-
Marketing
Compare campaigns on opens and clicks
Pull sends, opens and clicks across every active campaign and see which subject lines and sequences are earning attention this month.
-
Revenue operations
Track lead status changes for the week
List the leads created, who they were assigned to, and every status change since Monday, ready for the pipeline review.
-
Sales leadership
Pause a campaign before the holiday
Pause a whole campaign in Mailshake ahead of a quiet week, then unpause it when the team is back, without opening the app.
Try asking
- “Which recipients replied to the partners campaign this week?”
- “Add these 40 contacts to the Q3 outbound campaign”
- “Show lead status changes since Monday by owner”
AI tools
Mailshake tools for your AI agents
32 tools are ready to call through Elaichi's MCP endpoint the moment you connect Mailshake, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Mailshake gets you
6 screens from the product, each doing one job for your Mailshake account.
The agent
Ask about Mailshake campaigns in plain language.
Replies, opens and lead changes answered from live Mailshake records, not yesterday's export.
- campaigns
- recipients
- leads
- replies
Ask Elaichi to work across your apps.
Which recipients replied to the partners campaign this week?
Add these 40 contacts to the Q3 outbound campaign
Show lead status changes since Monday by owner
Also runs in Claude, ChatGPT or Cursor
MCP clients
Mailshake in Claude, ChatGPT and Cursor.
One governed endpoint for the whole organization, no SDK and no shared API key.
Copy the endpoint
Tool catalog
32 Mailshake tools, no code to write.
Campaigns, recipients, leads and activity covered end to end, ready the moment you connect.
- List all Mailshake me
- List all Mailshake campaigns
- Get single Mailshake campaign by ID
- Create a Mailshake campaign
Toolboxes
Every team gets its own Mailshake toolbox.
Outbound adds recipients, leadership reads results, each scoped to what that team needs.
- Outbound
- Sales
- Marketing
- Revenue operations
Shared connections
Share Mailshake without sharing the key.
One person connects, teammates work through it, nobody else ever sees a credential.
- Outbound US
- Outbound EMEA
- Partnerships
- Marketing
Audit log
Know who paused which Mailshake campaign.
Every campaign change, recipient added and lead read, logged with who and when.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Mailshake replies into action.
Replies fetched, grouped, drafted into a digest, approved by a person, posted back.
Mailshake digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch campaigns
Mailshake
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Mailshake
Queued
Collections and dashboards
Mailshake outreach health, computed without a model.
Four metrics, fourteen days of campaigns created, by team, refreshed on schedule.
Mailshake health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Recipients
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Outbound US 34%
Outbound EMEA 27%
Partnerships 21%
Marketing 18%
FAQ
Frequently asked questions
How do I connect Mailshake to Claude?
Connect Mailshake in Elaichi by pasting the API key from your Mailshake account, then add the Elaichi endpoint https://api.elaichi.ai/mcp in Claude under Customize, then Connectors, then Add. There is no OAuth application to register and no client ID or secret to generate. Once Claude is connected, your Mailshake campaigns, recipients and leads are available to it.
Does Mailshake work with ChatGPT and Cursor as well as Claude?
Yes. Once Mailshake is connected in Elaichi, the same endpoint https://api.elaichi.ai/mcp works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Mailshake once and every client picks it up.
What can an AI agent actually do with my Mailshake data?
An agent can list your Mailshake campaigns, create a new one, pause or unpause a campaign, and add recipients to it. It can also read who was sent to, who opened, clicked or replied, and follow leads as they are created, assigned and change status. Short concrete asks such as "replies on the Q3 partners campaign this week" work better than long paragraphs.
Does connecting Mailshake give the AI every campaign in the account?
The AI can only see what the Mailshake account behind the connected API key can see, and each person signs in to Elaichi as themselves, so the audit log names them. Elaichi can narrow that further by team, for example read only, or no campaign changes. It never widens access beyond what Mailshake already allows.
Can I stop an agent from deleting or changing things in Mailshake?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Mailshake campaigns, replies and leads while blocking creating campaigns, pausing them, or adding and unsubscribing recipients. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Mailshake connection when someone leaves?
Offboarding a person in Elaichi ends their access to the Mailshake connection at once, in every client they used. A shared Mailshake connection keeps working for everyone else on the team. If you disconnect Mailshake in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client in one step.
Put Mailshake in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.