Skip to content

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.

1

In Elaichi

Connect Mailshake once

  1. Open Connections, choose Add connection, and pick Mailshake.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

mailshake
Mailshake
Attentive
Beamer
beehiiv
Bird
Buffer
2

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.

Mailshake MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Mailshake MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Mailshake MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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”

See all 32 Mailshake tools below

Compare

Elaichi vs Zapier MCP vs Composio for Mailshake

All three can connect Mailshake to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Mailshake, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Mailshake tools Allow or restrict single Mailshake tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Mailshake call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Mailshake me List Get information about the current authenticated Mailshake user via the /me endpoint, which also serves as an authentication test. Returns: object, id, teamID, teamName, isTeamAdmin, isDisabled, emailAddress, fullName, first, last, teamBlockedDate.
List all Mailshake campaigns List List all Mailshake campaigns for a team. Returns each campaign with id, title, created, isArchived, isPaused, messages, sender, and url. An optional search filter narrows results by campaign title.
Get single Mailshake campaign by ID Get Get a single Mailshake campaign by campaignID, including its full message sequence. Returns the campaign object with id, title, created, isArchived, isPaused, messages, sender, and url. Required: campaignID. A not_found error is returned if the campaign could not be found.
Create a Mailshake campaign Create Create a new campaign in Mailshake. The campaign cannot be sent until the user completes the setup wizard in Mailshake's UI, but recipients can be added immediately. Returns the created campaign object including id, title, created, isArchived, isPaused, messages, sender, and url.
Mailshake campaigns pause Pause Pause all sending for a Mailshake campaign immediately. Emails in a batch currently being sent will not be stopped. Returns the campaign object including id, title, isPaused, isArchived, messages, and sender. Required: campaignID.

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
ElaichiToolboxes
Name Source template Tools Created

Outbound toolbox

Mailshake · campaigns and recipients

Mailshake starter 18 Mar 4, 2026

Sales toolbox

Mailshake · replies and leads

— 9 Mar 2, 2026

Marketing toolbox

Mailshake · opens and clicks

— 24 Feb 27, 2026

Revenue operations toolbox

Mailshake · lead assignments and status

Mailshake starter 6 Feb 19, 2026

Sales leadership toolbox

Mailshake · campaign performance

— 31 Jan 30, 2026

Client services toolbox

Mailshake · client campaign exports

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
MA

Mailshake (Outbound US)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MA

Mailshake (Outbound EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MA

Mailshake (Partnerships)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MA

Mailshake (Marketing)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
MA

Mailshake (Agency clients)

Connected by Ryan Hayes

Personal • Active Not shared
MA

Mailshake (Sales leadership)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Mailshake Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Mailshake Campaigns Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Mailshake Campaigns List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch campaigns

    Mailshake

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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 my team share one Mailshake connection?

Yes. One person connects Mailshake with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so every campaign change and every recipient added is logged under the person who did it.

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.

Does the Mailshake MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Mailshake is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Mailshake?

Yes. Both let Claude, ChatGPT or Cursor use Mailshake. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Mailshake call.

How is Elaichi different from Composio for Mailshake?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Mailshake: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Mailshake in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.