Read campaigns, replies and leads; pause or resume campaigns; close or reopen leads in Mailshake. For sales and outreach teams that run email campaigns and manage leads in Mailshake. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"mailshake": {
"url": "https://mailshake.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"mailshake": {
"type": "http",
"url": "https://mailshake.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the newest replies as plain text. Filter to real answers, or skip out-of-office messages, bounces and unsubscribe notices.
mailshake_list_replies
List the campaigns and find the campaign id. Then read its message sequence and list the recipients who opened, clicked or replied.
mailshake_list_campaigns mailshake_get_campaign mailshake_list_recipients
List the most recent email opens and clicks on tracked links. Use them to see which messages get attention.
mailshake_list_opens mailshake_list_clicks
Stop all sending for a campaign now. Emails already in a batch are not stopped. Resume the campaign when the fix is ready.
Changes data · mailshake_pause_campaign mailshake_unpause_campaign
Close a lead as won or lost, ignore it, or reopen it for review. The change does not send any email.
Changes data · mailshake_close_lead mailshake_ignore_lead mailshake_reopen_lead
The login page asks for your Mailshake API key.
Create the key in Mailshake → Extensions → API. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mailshake API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Mailshake connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
mailshake_get_account | read | 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 | read | List team members List the users on the team, for assigning leads. Mailshake: POST /team/list-members. |
mailshake_list_senders | read | List senders List the sender accounts (the mailboxes that send campaign emails). Mailshake: POST /senders/list. |
mailshake_list_campaigns | read | 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 | read | Get campaign Get one campaign and its message sequence. Mailshake: POST /campaigns/get. |
mailshake_list_recipients | read | 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 | read | 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 | read | 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 | read | 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 | read | List opens List the most recent email opens. Costs 2 quota units per call. Mailshake: POST /activity/opens. |
mailshake_list_clicks | read | List link clicks List the most recent clicks on tracked links. Costs 3 quota units per call. Mailshake: POST /activity/clicks. |
mailshake_list_created_leads | read | 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 | read | 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 | write | 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 | write | Unpause campaign Resume sending for a paused campaign. The sending calendar reschedules its pending emails. Mailshake: POST /campaigns/unpause. |
mailshake_pause_recipient | write | Pause recipient Stop all sending to one recipient in a campaign. Undo with mailshake_unpause_recipient. Mailshake: POST /recipients/pause. |
mailshake_unpause_recipient | write | Unpause recipient Resume sending to one paused recipient in a campaign. Mailshake: POST /recipients/unpause. |
mailshake_close_lead | write | Close lead Mark a lead as won (status closed, the default) or as lost (status lost). Mailshake: POST /leads/close. |
mailshake_ignore_lead | write | Ignore lead Mark a lead as not worth pursuing (ignored). Undo with mailshake_reopen_lead. Mailshake: POST /leads/ignore. |
mailshake_reopen_lead | write | Reopen lead Make a closed or ignored lead open again for review. Mailshake: POST /leads/reopen. |
mailshake_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
mailshake_request_feature | Request a missing feature Tell usefulapi that the user needs something the Mailshake tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
mailshake_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Mailshake (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
mailshake_cancel_subscription | Cancel the Pro subscription Cancel the caller's Mailshake Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run mailshake_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Mailshake server only. Subscribe with mailshake_upgrade (it returns a Stripe Checkout link). Cancel any time with mailshake_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running mailshake_upgrade before then undoes the cancel. Or write to [email protected].
Read the latest real replies. Review how a campaign performed. Check recent opens and link clicks. Pause a campaign while you fix it. Mark leads as won, lost or ignored. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Mailshake. The server calls the Mailshake API with your own Mailshake access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Mailshake API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mailshake API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Mailshake API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Mailshake.
Yes, if you approve it. 7 of the 20 Mailshake tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Mailshake server only. Cancel any time: Pro then runs to the end of the paid period. Run mailshake_usage_status to see how many calls you used.
Ask the AI to run mailshake_upgrade: it returns a Stripe Checkout link. To cancel, run mailshake_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with mailshake_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.