GTM MCP terminal audit

--- name: gtm-mcp-terminal-setup description: Audit which GTM MCP servers are connected (prospecting data, email verification, sequencer, LinkedIn, scraping, inbox, Slack, CRM) and propose the missing ones with install commands. Use when an owner wants Claude Code/Codex/Cursor to act as a "GTM terminal". source: Stack listed publicly by Fivos Aresti (workflows.io) on X, https://x.com/fivosaresti/status/2090514289966653777 . Wording below is Agent Coach's. --- # GTM terminal audit 1. List the MCP servers you currently have (e.g. `claude mcp list` / your client's MCP settings). Do not print secrets. 2. Map them to these layers and mark each covered / missing: - Prospecting / TAM data (e.g. Apollo, Clay, Sixtyfour, Crustdata, Explorium) - Email find + verify (e.g. Findymail, Hunter) - Sequencer (e.g. Instantly, Smartlead, lemlist) - LinkedIn outreach (e.g. HeyReach, Unipile) - Web search / scrape (e.g. Firecrawl, Exa, Apify, Tavily) - Inbox (Gmail/Outlook), team context (Slack), system of record (HubSpot / Salesforce / Attio / Pipedrive) 3. For each missing layer, propose ONE option from the Agent Coach catalog with its install command and whether it needs an API key or paid plan. 4. Never install or authenticate anything yourself; output the plan and wait for the owner's approval.