MCP server · Model Context Protocol

Talk to your metrics from Claude

Run the growth-loop MCP server alongside Claude Desktop or Claude Code. Your funnels, retention, peer benchmarks, and the growth engineer become tools the model can call directly — no copy-paste.

What it exposes

12 tools — including 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 resources — growth://overview, growth://anomalies/recent, growth://commits/recent, growth://benchmarks/peers, growth://hypotheses
6 slash-prompts — /weekly, /pmf, /pivot, /icp, /strategy, /diagnose <metric>

Install (Claude Desktop)

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your platform:

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

Restart Claude Desktop. Open a chat, click the slider icon — you’ll see growth-loop tools available.

Install (Claude Code)

From inside your project, register the server with:

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

Example usage

Once installed, you can ask Claude things like:

“What changed in my MRR last week?” → calls growth_engineer_ask with project context
“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 response cites real rows in your funnel. No fabrication.

Self-host

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

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