Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Mailshake in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Drive Mailshake (cold email / sales engagement) from any AI agent: campaigns, recipients, leads, replies. 8 tools, Basic auth (API key as user).
Try asking
Example prompts for Mailshake
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Mailshake, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Mailshake + Gemini
Drive Mailshake (cold email / sales engagement) from any AI agent: campaigns, recipients, leads, replies. 8 tools, Basic auth (API key as user).
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
MAILSHAKE_API_KEY
Step 1 — Get credentials
Setup:
- Sign in to https://mailshake.com → top-right avatar → API Keys → Create API Key.
- Set
MAILSHAKE_API_KEY.
Authentication: HTTP Basic with username=API_KEY, password=empty.
Campaign: a sequence of email steps. Add recipients to a campaign → they start receiving emails on schedule.
Recipient state: each recipient has a status (pending, sending, paused, finished, replied, bounced, unsubscribed).
Pagination: ?perPage=N&cursor=....
Out of scope here: campaign content editor (UI), team management, AI features, copy-A/B-testing config.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
- Save the file and restart
gemini. - Run
/mcpinside the Gemini CLI —Mailshakeshould be listed as available. - Vertex AI Studio: pass
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDto thetoolsarray of your request with the sameX-API-Keyheader.
Available tools
| Tool | What it does |
|---|---|
mailshake_me | Return the team the API key belongs to |
mailshake_list_campaigns | List campaigns |
mailshake_get_campaign | Get a campaign by ID |
mailshake_pause_campaign | Pause a campaign (stops all future sends until resumed) |
mailshake_unpause_campaign | Resume a paused campaign |
mailshake_add_recipients_to_campaign | Add recipients to a campaign |
mailshake_list_recipients | List recipients in a campaign with filters |
mailshake_pause_recipient | Pause a recipient by emailAddress + campaignID (stops further emails to them without unsubscribing) |
FAQ
Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with custom headers.
Next steps
Was this guide helpful?
