GrowthBook MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GB_USER | Yes | Your name. Used when creating a feature flag. | |
| GB_API_KEY | Yes | A GrowthBook API key. | |
| GB_API_URL | No | Your GrowthBook API URL. | https://api.growthbook.io |
| GB_APP_ORIGIN | No | Your GrowthBook app URL. | https://app.growthbook.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_environmentsB | Fetches all environments from the GrowthBook API. GrowthBook comes with one environment by default (production), but you can add as many as you need. Feature flags can be enabled and disabled on a per-environment basis. You can also set the default feature state for any new environment. Additionally, you can scope environments to only be available in specific projects, allowing for further control and segmentation over feature delivery. |
| get_projectsC | Fetches all projects from the GrowthBook API |
| get_sdk_connectionsC | Get all SDK connections, which are how GrowthBook connects to an app. Importantly, users need the key, which is a public client key that allows the app to fetch features and experiments the API |
| create_sdk_connectionC | Create an SDK connection for a user. Returns an SDK clientKey that can be used to fetch features and experiments. |
| create_feature_flagC | Create, add, or wrap an element with a feature flag. |
| get_feature_flagsC | Fetches all feature flags from the GrowthBook API. Flags are returned in the order they were created, from oldest to newest. |
| get_single_feature_flagC | Fetches a specific feature flag from the GrowthBook API |
| get_stale_safe_rolloutsC | Fetches all complete safe rollouts (rolled-back or released) from the GrowthBook API |
| generate_flag_typesB | Generate types for feature flags |
| get_experimentsC | Fetches all experiments from the GrowthBook API |
| create_force_ruleA | Create a new force rule on an existing feature. If the existing feature isn't apparent, create a new feature using create_feature_flag first. A force rule sets a feature to a specific value for a specific environment based on a condition. For A/B tests and experiments, use create_experiment instead. |
| get_experimentC | Gets a single experiment from GrowthBook |
| get_attributesD | Get all attributes |
| search_growthbook_docsC | Search the GrowthBook docs on how to use a feature |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes, such as create_feature_flag vs. create_force_rule, but there is some overlap between get_feature_flags and get_single_feature_flag, which could cause confusion if an agent needs to fetch a specific flag versus all flags. The descriptions help clarify, but the boundary is not perfectly clear.
The naming follows a consistent verb_noun pattern (e.g., create_feature_flag, get_experiments) with minor deviations like generate_flag_types (which uses 'generate' instead of 'get') and search_growthbook_docs (which includes 'growthbook' in the name). Overall, it is mostly predictable and readable.
With 14 tools, the count is well-scoped for a GrowthBook MCP server, covering key operations like creating flags, rules, connections, and fetching various resources. Each tool appears to earn its place without feeling excessive or insufficient for the domain.
The tool set provides good coverage for core GrowthBook operations, including CRUD-like actions for features, experiments, and connections, but there are minor gaps such as missing update or delete tools for flags or experiments, which agents might need to work around. The inclusion of search_growthbook_docs adds helpful context.