Skip to main content

MCP Server Configuration

Add the following MCP server configuration JSON to your respective tool’s config file. This config sets up the connection to Statsig’s MCP endpoint with your API key:
Replace console-YOUR-API-KEY with your actual Statsig Console API key, which you can retrieve here. Ensure your API key has the right permissions — read-only keys can view data, while write keys can make changes to your project! Once you’ve added and saved the configuration file, restart Cursor or Claude Desktop to apply the changes. After restarting, you should see the MCP server listed and active under the Developer settings. On Cursor, this can be found under Settings > Cursor Settings > Tools & Integrations.

Current MCP capabilities

Experiments (A/B Tests)

  • Get_List_of_Experiments: List all experiments in the project with optional status filtering
  • Get_Experiment_Details_by_ID: Get experiment details including groups and parameters
  • Create_Experiment: Create new experiments with groups, hypothesis, etc.
  • Update_Experiment_Entirely: Replace entire experiment configuration (any excluded data will be removed - the MCP will understand this.)

Gates (Feature Flags)

  • Get_List_of_Gates: List all gates/flags with optional type filtering (e.g., STALE, PERMANENT)
  • Get_Gate_Details_by_ID: Get complete gate configuration details (rules, ID type, etc.)
  • Create_Gate: Create new gate/flag with targeting rules and settings
  • Update_Gate_Entirely: Replace entire gate setup with new rules and settings (any excluded data will be removed - the MCP will understand this.)

Dynamic Configs

  • Get_List_of_Dynamic_Configs: List all dynamic config objects in the project
  • Get_Dynamic_Config_Details_by_ID: Retrieve detailed config including targeting rules, return values
  • Create_Dynamic_Config: Create new config with rules, return values, etc.
  • Update_Dynamic_Config_Entirely: Replace entire dynamic config with new targeting and values (any excluded data will be removed - the MCP will understand this.)
Need other functions? We’re happy to consider additions by request, reach out in Slack.

Setting up in Codex

This will update your ~/.codex/config.toml.

Setting up in Cursor

Click Here to add the Statsig MCP to Cursor, or copy the json to: ~/.cursor/mcp.json

Setting up in Claude Desktop

The configuration file is located at:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Setting up in Claude Code

On Claude Code, we recommend using the http transport directly, run this command on the command line anywhere you use Claude Code:

Use Cases

The Statsig MCP server now supports both GET and POST requests. This means tools can not only read data (like stale gates) but also make updates, if your API key has write permissions. We’ve found the Statsig MCP server especially useful for:
  • Repetitive tasks like cleaning up stale gates
  • Summarizing console information in your IDE workflows
  • Bulk creating or deleting gates, and making the necessary changes in your code

Example prompt for stale gate cleanup