MCP server · install guide

Connect growth-loop to your AI

Three steps: get a key, add the server to the tool you already use, ask a question. After that your funnels, retention, benchmarks and the growth engineer are tools the model calls directly — no copy-paste.

Step 1 · Get your API key

On Setup, click “Create my key” — it mints a pk_live_* key and fills it into every command below automatically if you install from there. Installing from this page instead? Replace pk_live_… in the snippets with your key.

Step 2 · Add the server — pick your tool

Cursor

Use the Install MCP button on Setup → Cursor → “Add to Cursor”. It opens Cursor’s own install dialog with everything pre-filled — approve and done. (Under the hood it’s a cursor:// deeplink carrying the config below.)

Claude Code

One command in your terminal, any directory:

claude mcp add growth-loop \
  -e GROWTH_API_KEY=pk_live_… \
  -e GROWTH_HOST=https://api.growth-loop.dev \
  -- npx -y @growth-loop/mcp-server

Claude Desktop

Settings → Developer → Edit Config opens claude_desktop_config.json. Add this and restart the app:

{
  "mcpServers": {
    "growth-loop": {
      "command": "npx",
      "args": ["-y", "@growth-loop/mcp-server"],
      "env": {
        "GROWTH_API_KEY": "pk_live_…",
        "GROWTH_HOST": "https://api.growth-loop.dev"
      }
    }
  }
}

Config lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows.

claude.ai (web & desktop connectors)

No install at all — we host the server. In Settings → Connectors → Add custom connector, enter:

URL:             https://api.growth-loop.dev/v1/mcp
Authentication:  Bearer Token
Token:           pk_live_…

growth-loop then shows up alongside Figma / Gmail / Drive in the connectors panel.

Step 3 · Ask a question

In an editor, run /growth-init — Claude detects your stack (Next.js / FastAPI / Express / Vite / Flask), installs the SDK, wraps the high-signal call sites and opens a PR you review. Nothing is auto-merged.

Or just talk to it — anywhere the server is connected:

  • “How is my product doing this week?” → calls overview
  • “Diagnose my signup-to-paid drop” → calls diagnose(signup_to_paid)
  • “Did my last commits hurt conversion?” → calls commits_list + diagnose
  • “How am I doing vs other B2C SaaS at this stage?” → calls peer_benchmark

Every answer cites real rows from your data. Nothing is fabricated.

Reference — everything the server exposes

  • 12 tools — the headline growth_engineer_ask(question) plus overview, funnel_get, retention, diagnose, why_event, peer_benchmark, commits_list, anomalies_list, hypotheses_list, metric_series, funnels_list
  • 5 resourcesgrowth://overview, growth://anomalies/recent, growth://commits/recent, growth://benchmarks/peers, growth://hypotheses
  • 6 slash-prompts/weekly, /pmf, /pivot, /icp, /strategy, /diagnose <metric>

Troubleshooting

  • Tools don’t appear — restart the client (Desktop needs a full restart after config edits). In Claude Code, check claude mcp list.
  • 401 / unauthorized — the key is wrong or revoked. Mint a fresh one on Setup and update the env / token.
  • npx can’t find the package — needs Node 18+; check node -v.

Self-host

The server is open source. Clone, adjust, run:

git clone https://gitlab.com/AKnyaZP/metrics
cd metrics/packages/mcp-server
pnpm install && pnpm build
node dist/index.js