GTM Alpha API and MCP docs

Overview

GTM Alpha offers three go to market analysis tools over the Model Context Protocol (MCP). They work in Claude, Cursor and other MCP compatible clients.

What you can do

• Get a free EPIC audit summary using the EPIC framework
• Get EPIC framework scores for a GTM situation
• Generate a GTM implementation roadmap

MCP setup

Add GTM Alpha to your MCP compatible client by setting the server endpoint.

Server URL: https://gtmalpha.gtmhelix.com/mcp. Transport: Streamable HTTP (POST requests, JSON responses). Authentication: none. The older address /mcp-sse answers the same way.

Claude (web, desktop and mobile)

Open Customize, then Connectors, select + and choose Add custom connector. Enter the server URL above, leave the sign in fields empty, then select Add.

Claude Code

claude mcp add --transport http gtm-alpha https://gtmalpha.gtmhelix.com/mcp

Run locally (npm, stdio)

{
  "mcpServers": {
    "gtm-alpha": {
      "command": "npx",
      "args": ["-y", "@shashwatgtmalpha/gtm-alpha-mcp-server"]
    }
  }
}

Cursor

{
  "mcpServers": {
    "gtm-alpha": {
      "url": "https://gtmalpha.gtmhelix.com/mcp"
    }
  }
}

VS Code

{
  "servers": {
    "gtm-alpha": {
      "type": "http",
      "url": "https://gtmalpha.gtmhelix.com/mcp"
    }
  }
}

Available tools

GTM Alpha provides the following MCP tools, all free:

API endpoints

Rate limits: the /api paths share 30 requests a minute per visitor, and the MCP server allows 300 a minute. If you go over a limit, the server returns 429 (Too Many Requests).

Authentication

No authentication is required. All tools are free to use.

Limits and when not to use GTM Alpha

All three tools are read only and return analysis as text. Scores run from 1 to 10. Without the optional inputs (contract value, deal cycle, net revenue retention, target accounts, self serve, deal source, region), the result is marked preliminary. The MCP endpoint answers POST requests only, and other methods return 405. GTM Alpha is not the right tool for:

• Teams that want a strategy written by AI: the EPIC scores follow fixed rules from the documented rubric, and no AI model writes them.
• Companies that cannot share basic numbers: if contract value, deal cycle, net revenue retention or target account count is missing, the result is marked preliminary.
• Anyone who needs live market data: GTM Alpha does not look anything up and works only from what you enter.
• Anyone who needs a tool that writes to a CRM or other systems: all three tools are read only and return analysis only.

Usage examples

Try these prompts

• Use GTM Alpha to run an EPIC audit: telecom (managed SD-WAN and business internet for companies with many branches), Series B, deal cycle 150 days, ACV $240,000, not self serve, most deals come through outbound, selling in India.
• Use GTM Alpha to run a free EPIC audit for a spend management software company (every figure here is an example): Series A, ACV $24,000, deal cycle 60 days, 9,000 target accounts, not self serve, mostly inbound, India. We want to win midsize companies that have a finance controller and an ERP.
• Use GTM Alpha to build a 60 day GTM roadmap focused on the Ecosystem motion.

Using with Claude

Once it is set up, ask Claude to use the GTM Alpha tools:

Use the GTM Alpha epic_audit tool to score the GTM situation of
a B2B SaaS company in the HR tech space selling an AI recruitment
platform to mid-market companies (100-1000 employees).

MCP request example (cURL)

curl -X POST https://gtmalpha.gtmhelix.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "epic_audit",
      "arguments": {
        "challenge": "B2B SaaS in HR tech selling to mid-market companies",
        "industry": "HR Tech",
        "business_stage": "series-a",
        "acv_usd": 24000,
        "deal_cycle_days": 60,
        "nrr_percent": 105,
        "tam_accounts": 8000,
        "deal_source": "outbound",
        "geography": "india"
      }
    }
  }'

Release history

History: first commit on 13 July 2025, first npm release on 8 September 2025, and listed in the MCP Registry since 11 December 2025. Versions and dates below come from the git history of this site's code, from npm and from the MCP Registry (checked 27 September 2026). npm has 1.0.0 to 1.0.5 and 1.2.0, its latest version, published 24 September 2026. Versions 1.1.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9, 1.3.12, 1.3.13, 1.3.17 and 1.3.20 run on this site only and are not on npm, so the npm package can lag behind this site. The MCP Registry lists 1.0.2 and 1.0.5.