GrowthBook MCP Server for Claude
Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server.
Open the source and read safety notes before installing.
Safety notes
- `create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions.
- Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming.
Privacy notes
- Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context.
- Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files.
Prerequisites
- A GrowthBook account (cloud at growthbook.io or self-hosted).
- A GrowthBook API key (from API Keys settings or a Personal Access Token with appropriate permissions).
- Your GrowthBook account email (used when creating experiments and feature flags).
- Node.js with `npx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://growthbook.io
- Disclosure
- GrowthBook is an open-source A/B testing and feature flag platform. The MCP server is officially maintained by GrowthBook.
Full copyable content
{
"mcpServers": {
"growthbook": {
"command": "npx",
"args": ["@growthbook/growthbook-mcp"],
"env": {
"GB_API_KEY": "your-api-key",
"GB_EMAIL": "you@example.com"
}
}
}
}About this resource
Overview
The GrowthBook MCP Server is the official Model Context Protocol server from GrowthBook, the open-source A/B testing and feature flag platform. It connects Claude directly to your GrowthBook workspace — listing and creating experiments, managing feature flags, reviewing experiment results, and more. Permissions follow your API key's access level. Licensed under MIT.
Supports both GrowthBook Cloud (api.growthbook.io) and self-hosted instances via the
GB_API_URL and GB_APP_ORIGIN environment variables.
Key capabilities
- Experiments — list experiments, get details and results, create new A/B tests.
- Feature flags — list feature flags, create new flags, update targeting rules.
- Self-hosted support — point to any GrowthBook instance via
GB_API_URL. - Custom headers — add tenant IDs, auth tokens, or proxy headers via
GB_HTTP_HEADER_<NAME>environment variables.
How it compares
| Server | A/B experiments | Feature flags | Self-hosted | Auth |
|---|---|---|---|---|
| GrowthBook MCP | Yes | Yes | Yes | API key |
| LaunchDarkly MCP | No | Yes | Limited | API key |
| Unleash MCP | No | Yes | Yes | PAT |
| ConfigCat MCP | No | Yes | Yes | API key |
GrowthBook is the only open-source option with native A/B experiment management alongside feature flags — giving full control over the experiment lifecycle from Claude.
Installation
Claude Code
claude mcp add growthbook \
-e GB_API_KEY=your-api-key \
-e GB_EMAIL=you@example.com \
-- npx @growthbook/growthbook-mcp
Claude Desktop
{
"mcpServers": {
"growthbook": {
"command": "npx",
"args": ["@growthbook/growthbook-mcp"],
"env": {
"GB_API_KEY": "your-api-key",
"GB_EMAIL": "you@example.com"
}
}
}
}
Self-hosted GrowthBook
{
"env": {
"GB_API_KEY": "your-api-key",
"GB_EMAIL": "you@example.com",
"GB_API_URL": "https://your-growthbook.example.com/api",
"GB_APP_ORIGIN": "https://your-growthbook.example.com"
}
}
Requirements
- A GrowthBook account with an API key and your account email.
- Node.js with
npx. - An MCP client (Claude Code or Claude Desktop).
Security
- Capabilities are scoped by your API key's permissions — use a least-privilege key.
- Feature flags and experiments may affect production; review before creating or modifying.
Source Verification Notes
Verified on 2026-06-18:
- Official GitHub repository
growthbook/growthbook-mcp(MIT) documents the@growthbook/growthbook-mcpnpm package,GB_API_KEY/GB_EMAIL/GB_API_URL/GB_APP_ORIGINconfiguration,GB_HTTP_HEADER_*custom headers, and the official docs link. - GrowthBook documentation at
docs.growthbook.io/integrations/mcp(HTTP 200) covers setup and available capabilities. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the stdio connector pattern used above.
Source citations
Add this badge to your README
How it compares
GrowthBook MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | GrowthBook MCP Server for Claude Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server. Open dossier | Mixpanel MCP Server for Claude Query Mixpanel analytics data from Claude — run insights, funnels, flows, retention analysis, manage dashboards, explore events and properties, run experiments, and analyze session replays — with the official Mixpanel remote MCP server. Open dossier | Unleash MCP Server for Claude Create and manage Unleash feature flags from Claude — evaluate whether a change needs a flag, detect existing flags to prevent duplicates, set rollout strategies, toggle environments, and get cleanup guidance — with the official Unleash MCP server following Unleash best practices. Open dossier | ConfigCat MCP Server for Claude Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | GrowthBook | Mixpanel | Unleash | ConfigCat |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming. | ✓The server is hosted by Mixpanel and authenticated via OAuth — your existing Mixpanel project permissions are automatically applied. The MCP server grants read and write access to your Mixpanel project; it can create and modify dashboards, reports, and feature flags. Treat Service Account credentials as secrets; do not commit them to repositories. | ✓`toggle_flag_environment` enables or disables a feature flag in a production environment — confirm before toggling live flags. `create_flag` writes to your Unleash instance; capabilities are scoped by your PAT's permissions. Remote MCP (`--transport http`) is experimental and must be enabled on your Unleash instance. | ✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs. |
| Privacy notes | ✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files. | ✓Queries and analytics results (event data, user properties, funnel metrics) are sent through Mixpanel's hosted MCP infrastructure. Session replay summaries and user segment data may surface in Claude's context — treat these as sensitive product analytics. | ✓Feature flag names, descriptions, targeting rules, rollout configurations, and project metadata from your Unleash instance are surfaced in Claude's context. Your `UNLEASH_PAT` is a secret — store it as an environment variable and do not commit it to version control. | ✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.