Skip to main content

​
Overview

You can set up the Statsig MCP server using an API key on Codex CLI, IDE Extension, and App today.

​
Installation and Authentication via OAuth

MCP OAuth only supports Personal Console API Keys. Ensure your Statsig org owner has enabled Personal Console API Keys creation for your role here
On Codex, we recommend using OAuth and the HTTP transport directly. Authentication will be saved for future sessions.
In Codex Desktop, navigate to Settings > MCP servers and add a new custom server. Set up via Streamable HTTP, with URL set to https://api.statsig.com/v1/mcp:Set up Statsig MCP in the Codex Desktop AppUpon saving, you should see statsig turned on under custom servers.Statsig MCP in the Codex Desktop App MCP Servers List
[mcp_servers.statsig]
url = "https://api.statsig.com/v1/mcp"
command = "npx"
args = ["--yes", "mcp-remote", "https://api.statsig.com/v1/mcp", "--header", "statsig-api-key: console-YOUR-CONSOLE-API-KEY"]
trust_level = "trusted"
enabled = true
Replace console-YOUR-CONSOLE-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!

​
Using Statsig MCP with Codex

With Statsig MCP configured in any Codex environment, you can:
  • Explore Experiments: “List all my active experiments”
  • Manage Gates: “What gates are currently stale?”
  • Configure Dynamic Configs: “Show me the configuration for the dynamic config ‘dynamic-config’”
  • Get Insights: “Show me details about the experiment called ‘new-checkout-flow‘“

​
Next Steps

After installation, you can:
  • List experiments, gates, and dynamic configs
  • Create and update experiments, gates, and configs
  • Access your Statsig data directly from Codex
For more information about available MCP capabilities, see the MCP capabilities section.