Issue #1: 32 GTM tools with official MCP servers, verified

Published: 2026-10-15 · StackMCP Issue #1 (web archive — not an email)


Week zero: the baseline

StackMCP (https://mcpforgtm.com) tracks which go-to-market tools have official MCP servers: the endpoint, the auth model, and what your agent can actually call.

Nothing broke yet, because this is the first issue. Instead, here's the starting line. On 2026-10-15 we checked 32 GTM-relevant MCP listings against vendor docs. Starting next week, each issue leads with outages, auth changes, and removed tools.


By the numbers


Four things to know before you wire one up

  1. Don't assume one auth pattern. Instantly is API-key-first. Clay and Attio use OAuth, and Apollo uses OAuth with a master API key option for headless use.
  2. Remote and local servers aren't interchangeable. ZeroBounce and some packages are stdio-only, so they won't work in a Claude custom connector URL field.
  3. A directory listing isn't proof. We mark an endpoint verified only when vendor docs or a live auth challenge back it up. PredictLeads, for example, is listed with a hosted-MCP claim, but we haven't confirmed the endpoint yet, so don't rely on a connector URL for it.
  4. A ChatGPT or Claude connector isn't the same as an MCP URL. Some vendors ship directory connectors and raw Streamable HTTP endpoints. Use the vendor docs link on each StackMCP tool page.

Verified remote endpoints

18 of the 27 remote endpoints, in no particular order. The full list, including regional and local variants, is at https://mcpforgtm.com/.

Prospecting and enrichment

Outreach, CRM, and scheduling

Workflow, data, and content


What we'll flag starting next week

Spot something broken before we do? Tell us via get verified or subscribe / contact from the newsletter page.


Vendors: get your MCP server verified at https://mcpforgtm.com/get-verified.html

Know someone wiring agents into a sales stack? Send them https://mcpforgtm.com/newsletter.html

← All issues · Subscribe