Growthbook MCP logo

Growthbook MCP

by growthbook

Connects AI agents to GrowthBook’s REST API and guided feature-flag workflows through MCP.

Install Growthbook MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "growthbook-growthbook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@growthbook/mcp"
      ],
      "env": {
        "GB_API_KEY": "YOUR_VALUE_HERE",
        "GB_API_URL": "YOUR_VALUE_HERE",
        "GB_MCP_TRANSPORT": "YOUR_VALUE_HERE",
        "GB_MCP_PORT": "YOUR_VALUE_HERE",
        "GB_MCP_HOST": "YOUR_VALUE_HERE",
        "GB_MCP_URL": "YOUR_VALUE_HERE",
        "GB_OAUTH_ISSUER": "YOUR_VALUE_HERE",
        "GB_SKILLS_ENABLED": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 4 tools correctly (1mo ago).

Overview

The growthbook/growthbook-mcp MCP server exposes GrowthBook feature-flag and experimentation workflows through MCP tools. It combines authenticated REST API requests with skills that describe how to complete common GrowthBook tasks. Use it when an agent needs to inspect or modify GrowthBook resources, create feature flags, or follow bundled workflow guidance. API keys or personal access tokens are supported for stdio use, while HTTP mode can use GrowthBook OAuth.

Use cases

  • List GrowthBook projects and feature flags
  • Create or update GrowthBook feature flags
  • Read bundled workflows for experimentation tasks
  • Run authenticated GrowthBook REST API requests
  • Expose GrowthBook API access over HTTP

Key features

  • GrowthBook REST API passthrough
  • Feature-flag and experiment workflows
  • Bundled agent skills
  • Stdio and HTTP transports
  • OAuth support for HTTP mode
  • Configurable request headers

Tools4

What Growthbook MCP lets your agent do. Expand a tool for its parameters.

Verified live~597 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

18/18 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @growthbook/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars24Stargazers on the source repository.
npm downloads28kPackage downloads in the last 30 days.
Last commit19d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Growthbook MCP works

What growthbook/growthbook-mcp MCP server does

The growthbook/growthbook-mcp MCP server gives an MCP client access to GrowthBook’s REST API and bundled agent skills. It is intended for tasks involving GrowthBook feature flags, experiments, and related API resources. The server does not provide a separate formatter for each endpoint; agents send requests to the GrowthBook REST API and receive the raw response body for successful calls.

The repository describes a thin server whose task-specific knowledge comes from a skills collection bundled during the build. Skills provide workflows and guardrails, while the API tool performs the requests those workflows describe. This keeps the server focused on exposing GrowthBook operations rather than implementing a separate abstraction for every API resource.

How it works

An agent can first call growthbook_list_skills to see available top-level workflows. It can then use growthbook_read_skill to load a complete workflow or a qualified child workflow, such as a feature-flag creation reference. The workflow may describe commands such as gb-call GET /api/v1/projects; the MCP server maps those instructions to its GrowthBook API request capability instead of executing the shell command.

Read operations use GET requests. Write operations use POST, PUT, PATCH, or DELETE requests and may include a JSON body. The server distinguishes read and write capabilities so MCP clients can identify read-only and potentially destructive actions. Agents should obtain confirmation before a mutation unless the user has already explicitly requested it.

The server defaults to stdio. It can also run as a standalone HTTP service with MCP endpoints at /mcp and /mcp/api. The full endpoint exposes skills and API operations, while the capability-only endpoint exposes API read and write operations.

Setup and configuration

Install dependencies and build the project with:

Terminal
npm install
npm run build

A published release can be started with npx @growthbook/mcp. For stdio, configure the MCP client to run the package or the compiled Node entrypoint and provide GB_API_KEY. This value can be a GrowthBook API key or personal access token. GB_API_URL defaults to https://api.growthbook.io and can point to a self-hosted GrowthBook installation.

Set GB_MCP_TRANSPORT=http for HTTP mode. HTTP mode requires GB_MCP_URL, which identifies the public MCP base URL used in OAuth resource metadata. GB_MCP_PORT defaults to 3333, and GB_MCP_HOST defaults to 127.0.0.1. GB_OAUTH_ISSUER can override the OAuth issuer, which otherwise follows GB_API_URL.

Tools and capabilities

  • List available GrowthBook skills and their descriptions.
  • Read full skill workflows and qualified child references.
  • Send authenticated GET requests to GrowthBook REST API paths.
  • Send authenticated POST, PUT, PATCH, and DELETE requests with optional JSON bodies.
  • Disable skill tools with GB_SKILLS_ENABLED=false or 0 when only API access is needed.
  • Add extra request headers through variables prefixed with GB_HTTP_HEADER_.

The growthbook/growthbook-mcp MCP server returns actionable errors for non-successful API responses, including authentication failures, rate limits, and some self-hosted API path issues. In HTTP mode, rejected bearer tokens are surfaced as HTTP 401 responses so clients can refresh them; a 403 is treated as an accepted token with insufficient permission.

Limitations and notes

The server depends on access to a GrowthBook API and valid credentials for authenticated use. Skill content is bundled at build time from the canonical skills repository, with the selected commit controlled by the project’s lock file. Local builds can use a configured skills checkout, so the available workflows may depend on the build source.

The growthbook/growthbook-mcp MCP server does not execute the gb-call shell adapter referenced by skill documentation. Agents must translate those instructions into the MCP API request tool. HTTP deployments intended for public or multi-tenant use should be placed behind the deployer’s own gateway or authentication controls.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Growthbook MCP

Run `npx @growthbook/mcp` for the published package, or clone the repository, run `npm install`, and build it with `npm run build`.

Stdio mode requires `GB_API_KEY`, which can be a GrowthBook API key or personal access token. HTTP mode can use GrowthBook OAuth.

Yes. Its API write capability supports POST, PUT, PATCH, and DELETE requests, and bundled skills include feature-flag workflows.

Yes. Set `GB_MCP_TRANSPORT=http`; HTTP mode requires `GB_MCP_URL` and exposes MCP at `/mcp`, with API-only access at `/mcp/api`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGrowthbook MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/growthbook-growthbook-mcp?style=directory)](https://allmcps.com/mcp/growthbook-growthbook-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/growthbook-growthbook-mcp"><img src="https://allmcps.com/api/badge/growthbook-growthbook-mcp?style=directory" alt="Growthbook MCP on AllMCPs" /></a>