Mailshake MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://mailshake.usefulapi.io/mcp

claude mcp add --transport http mailshake https://mailshake.usefulapi.io/mcp

{
  "mcpServers": {
    "mailshake": {
      "url": "https://mailshake.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "mailshake": {
      "type": "http",
      "url": "https://mailshake.usefulapi.io/mcp"
    }
  }
}

https://mailshake.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• mailshake_get_account

  Show the signed-in Mailshake user and team. Also the cheapest call to check the API key. Mailshake: POST /me.

• mailshake_list_team_members

  List the users on the team, for assigning leads. Mailshake: POST /team/list-members.

• mailshake_list_senders

  List the sender accounts (the mailboxes that send campaign emails). Mailshake: POST /senders/list.

• mailshake_list_campaigns

  List the team's campaigns with their IDs and status. Start here to find a campaignID. Costs 10 quota units per call. Mailshake: POST /campaigns/list.

• mailshake_get_campaign

  Get one campaign and its message sequence. Mailshake: POST /campaigns/get.

• mailshake_list_recipients

  List the recipients of one campaign. Filter by state (for example opened, clicked, replied, wasSent, bounced, paused, hasProblems); set negateAction to exclude that state. Costs 10 quota units per call. Mailshake: POST /recipients/list.

• mailshake_list_leads

  List the team's leads: recipients who may be interested. Filter by campaign, status (for example open) or the teammate the lead is assigned to. Costs 1 quota unit per call. Mailshake: POST /leads/list.

• mailshake_list_sent_messages

  List the most recent emails sent, with the recipient and the message text as plain text. Costs 1 quota unit per call. Mailshake: POST /activity/sent.

• mailshake_list_replies

  List the most recent replies, with the reply text as plain text. Use replyType reply for real answers; bounce, out-of-office, unsubscribe and delay-notification are the other kinds. Costs 10 quota units per call. Mailshake: POST /activity/replies.

• mailshake_list_opens

  List the most recent email opens. Costs 2 quota units per call. Mailshake: POST /activity/opens.

• mailshake_list_clicks

  List the most recent clicks on tracked links. Costs 3 quota units per call. Mailshake: POST /activity/clicks.

• mailshake_list_created_leads

  List the most recently created leads (from Lead Catcher rules or manual conversions). Costs 5 quota units per call. Mailshake: POST /activity/created-leads.

• mailshake_list_lead_status_changes

  List the most recently updated leads (opened, won, lost or ignored). Costs 5 quota units per call. Mailshake: POST /activity/lead-status-changes.

• mailshake_pause_campaign

  Stop all sending for a campaign now. Emails already in a batch are not stopped. Undo with mailshake_unpause_campaign. Mailshake: POST /campaigns/pause.

• mailshake_unpause_campaign

  Resume sending for a paused campaign. The sending calendar reschedules its pending emails. Mailshake: POST /campaigns/unpause.

• mailshake_pause_recipient

  Stop all sending to one recipient in a campaign. Undo with mailshake_unpause_recipient. Mailshake: POST /recipients/pause.

• mailshake_unpause_recipient

  Resume sending to one paused recipient in a campaign. Mailshake: POST /recipients/unpause.

• mailshake_close_lead

  Mark a lead as won (status closed, the default) or as lost (status lost). Mailshake: POST /leads/close.

• mailshake_ignore_lead

  Mark a lead as not worth pursuing (ignored). Undo with mailshake_reopen_lead. Mailshake: POST /leads/ignore.

• mailshake_reopen_lead

  Make a closed or ignored lead open again for review. Mailshake: POST /leads/reopen.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 14 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 20 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32357 servers in this category
• Published to the registry more recently than 98% of the other 32357 servers in this category
• Basic checks equal to or better than 100% of the other 32357 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{