Integration · GrowthBook

Open-source warehouse-native experimentation.

GrowthBook runs SQL on your existing data stack. The platform is fully open source, the MCP is open source, and customers include Dropbox, Khan Academy, and Mistral.

GrowthBook claims the first open-source production MCP for experimentation. The MCP runs locally and talks to your GrowthBook instance with an API key. Because the platform is warehouse-native, no event data leaves your stack to power the experiment math; the MCP is just the agent surface on top of it.

Official MCPApache 2.0. Self-host or cloud.

What you can do via MCP

Example prompts the agent runs.

  • Set up an A/B test for the new pricing page with 50/50 traffic split.

    Creates the experiment in GrowthBook with the right targeting and primary metric, returns the SDK snippet for the integration.

  • Wrap every new feature in a flag, gradually deploy.

    Generates a per-feature flag config plus a rollout schedule the agent follows over days or weeks.

  • Identify and clean up stale flags. Schedule weekly.

    Pulls the flag list, scores by last evaluation, opens a PR removing dead flag references, and registers the cleanup as a recurring task.

  • Give me an update on my banner test for the pricing page.

    Fetches results, summarizes lift and confidence, calls out segment differences, and recommends a next step.

  • Analyze all past checkout flow experiments. Find top 3 win/lose reasons.

    Reads experiment history, clusters outcomes, and ships a brief on what consistently moves checkout completion.

GrowthBook · MCP

Local MCP server invocation. The agent connects with the API key from GrowthBook account settings.

GrowthBook MCP
docs
# GrowthBook OSS MCP, local server
# Run: GROWTHBOOK_API_KEY=key_abc123 npx growthbook-mcp

mcp.growthbook.create_experiment({
  trackingKey: "pricing-page-v2",
  name: "Pricing page A/B",
  hypothesis: "New tier hierarchy increases paid conversion.",
  variations: [
    { id: "0", name: "Control", weight: 0.5 },
    { id: "1", name: "Treatment", weight: 0.5 }
  ],
  metrics: ["paid_signup"],
  datasource: "snowflake_prod"
})

# Runs SQL on your warehouse; results stay in your stack
One command sample showing how the agent talks to GrowthBook. The MCP exposes the platform's primitives as tools; the agent translates the prompt into the right call.

MCP integration

GrowthBook MCP server.

Server
github.com/growthbook/growthbook-mcp (clone and self-host)
Auth
GrowthBook API key (Account > API Keys)
Hosting
Local
  • 100% open source MCP plus open source platform
  • Warehouse-native: experiment math runs on your data stack (Snowflake, BigQuery, Redshift, ClickHouse, Postgres)
  • No event data leaves your stack; MCP is the agent surface only
  • Self-host GrowthBook or use GrowthBook Cloud; MCP works against either

GrowthBook MCP repo

Visual demonstration

What this looks like in practice.

GrowthBook/Experiment results
Ship treatment

pricing-page-v2

Primary metric: paid_signup (warehouse SQL)

VariantMetricLift95% CIp
Controlcontrol5.10%baseline
Treatment5.42%+6.27%[1.20, 11.40]0.018
Running
28d
N
412,800

Result computed by SQL against the prod warehouse. Effect significant at 95%. Recommendation: ship.

GrowthBook results delivered through the MCP. Underlying SQL runs on the team's warehouse; event data never leaves the stack.
GrowthBook· Stale flag audit
3 stale of 4
  • old-onboarding-v1

    Stale

    Last evaluated 92 days ago · @jess

    Removed in last quarter; references still in code

    Remove
  • checkout-button-color

    Stale

    Last evaluated 47 days ago · @karim

    Decided experiment, ship variant on; flag still gating

    Remove
  • new-pricing

    Active

    Last evaluated 2 hours ago · @maya

    Active rollout at 30%, evaluating

    Keep
  • experimental-search

    Stale

    Last evaluated 61 days ago · @dani

    Killed experiment, code path no longer reached

    Remove
The agent's scheduled stale-flag audit. The MCP plus a codebase grep gives the agent the data it needs to open the right cleanup PR.

CLI alternative

REST API for non-MCP workflows.

GrowthBook has a full REST API for direct integration outside an agent runtime. For AI-driven experiment work the MCP is the right interface; the REST API covers CI integration, scheduled reports, and any case where running an agent would be excessive.

Pairs with these skills

The PM-experimentation skill suite.

This integration pairs with the forthcoming experiment-design, feature-flagging skills. The skill landing pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.