$ man how-to/mcp-gtm-stack

If you run pipeline, outbound, or revenue operations, your core MCP stack connects your campaign tools to your AI agent. The goal is zero tab-switching. Instead of jumping between Instantly, HeyReach, Slack, and Sheets to check campaign status, you ask Claude. Claude pulls the data, analyzes it, and gives you a summary. The GTM stack is not about connecting everything. It is about connecting the tools that sit in your daily workflow loop: the ones you check repeatedly, export from manually, and copy-paste between.

PATTERN

Instantly manages email sequences, deliverability, and domain warming. The MCP server lets Claude check campaign analytics, pull reply lists, manage leads, and monitor deliverability scores without opening the Instantly dashboard. Setup: Get your API key from Instantly settings. Add it to your MCP config. The server exposes tools for listing campaigns, fetching analytics, and managing leads. Real workflow: /instantlyreplies_acme pulls all replies from the Acme campaign, saves them to the partner resources folder, and flags positive replies for follow-up. Zero manual export. Zero CSV downloads. Claude reads the replies and categorizes them.

PATTERN

HeyReach manages LinkedIn connection requests, messaging sequences, and campaign analytics. The MCP server lets Claude export accepted connections, pull campaign stats, and check message status. Setup: API key from the HeyReach dashboard. HTTP-based MCP server. Real workflow: /heyreach-export accepted exports all accepted connections from a campaign as a CSV. /heyreach-conversations pulls the full LinkedIn message history for accepted connections. The handoff workflow exports both accepted and unaccepted leads, runs deep research on accepted ones, and routes everything to the caller with a Slack notification.

PATTERN

Slack MCP reads channels, sends messages, and searches history. Essential for partner comms. The /slacksync skill pulls the full channel history and extracts action items, decisions, and deliverables into a structured markdown file. Google Sheets MCP reads and writes spreadsheets. Bridges your repo with team data. Push enrichment results to a shared sheet. Pull lead lists for campaign setup. Firecrawl MCP scrapes websites as clean markdown. Critical for enrichment workflows. Pull a prospect's website, extract positioning, identify pain points. Claude processes the raw HTML into structured data your qualification prompts can use. Each of these serves a specific purpose in the GTM loop: Slack for communication, Sheets for shared data, Firecrawl for research.

FORMULA

The GTM MCP stack creates a closed loop. Firecrawl scrapes prospect websites for research. The research feeds into Clay qualification prompts. Qualified leads route to Instantly (email) or HeyReach (LinkedIn). Reply data flows back through the MCP. Slack notifications alert the team. Sheets track the pipeline. Every step in this loop used to require manual work: export, download, upload, copy, paste. With MCPs, Claude handles the data movement. You handle the strategy and the conversations. The MCP stack does not replace your judgment. It replaces the grunt work between your judgment calls.