# Mailshake: MCP server status, API access gate and what it does > Sales engagement platform for automated email outreach campaigns with CRM integration and lead management. No MCP found, Paid, self-serve. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Engagement & Outbound](../categories/engagement-outbound.md) / Mailshake # Mailshake [No MCP found](../mcp/none-found.md) [Paid, self-serve](../gates/paid.md) [Engagement & Outbound](../categories/engagement-outbound.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [mailshake.com](https://mailshake.com) · entry id 02-mailshake · source 02-engagement-outbound.md line 255 **What it does** Sales engagement platform for automated email outreach campaigns with CRM integration and lead management. **AI features, separated from automation with an AI label on it** "AI Email Writer" auto-generates draft copy - genuinely AI/LLM-based per vendor. An "AI Sales Coach" is referenced in feature lists but not detailed on sourced pages. No AI-agent/autonomous-SDR claims found, unlike most competitors here. **RevOps role** Outbound email sequencing layer with light AI copy-drafting assistance; more modest AI positioning than most peers. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: n/a **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Paid, self-serve - **Can a solo operator reach it**: Yes, by paying, no sales call api_gate, verbatim from the file: paid (the API key is self-served from Extensions > API inside the product with no plan restriction stated, and the cheapest plan is Starter at $29/mo - there is no free plan) **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** [github.com/mailshake](https://github.com/mailshake) tied to the vendor by rule 3, account website https://mailshake.com has the vendor's domain, confidence strong - **Public repositories**: 1, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-06-25 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [mailshake-node](https://github.com/mailshake/mailshake-node) | SDK | Node.js library for the Mailshake API | 1 | 2026-06-25 | v3.0.0 | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **Jobs it can do** - [Run an email sequence](../jobs/run-email-sequence.md) - [Draft personalized outreach](../jobs/draft-personalized-outreach.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [http://mailshake.com/pricing/](http://mailshake.com/pricing/) - [http://mailshake.com/](http://mailshake.com/) - [https://api-docs.mailshake.com/](https://api-docs.mailshake.com/) 3 source URLs. Raw sources field, verbatim: http://mailshake.com/pricing/, http://mailshake.com/, https://api-docs.mailshake.com/ **Notes, verbatim from the file** Site serves over plain HTTP with a redirect, a minor hygiene flag for a company selling email infrastructure. No API tier information was found on sourced pricing pages. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://api-docs.mailshake.com/): the API key is self-served from Extensions > API inside the product with no plan restriction stated, and the cheapest plan is Starter at $29/mo - there is no free plan. 2026-09-02: re-checked mailshake.com/llms.txt (404) and web search; only Zapier MCP and AnythingMCP aggregator connectors surface, no MCP server found. **Provenance** - **Entry id**: 02-mailshake - **Source file**: 02-engagement-outbound.md - **Source line**: 255 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).