Statsig MCP

Use the Statsig MCP server to inspect and manage Statsig entities, review rollout state, check experiment or gate results, inspect audit history, and answer configuration questions.

Connection and setup

First check for an available Statsig MCP connection and inspect its advertised tools. Use an existing connection, including v1, according to its actual schemas; installing this skill does not migrate the server or refresh the client's tool catalog.

For a new connection, use https://api.statsig.com/v3/mcp. For example, add this server to ~/.codex/config.toml, replacing the placeholder locally with a Console API key:

[mcp_servers.statsig]
command = "npx"
args = ["--yes", "mcp-remote", "https://api.statsig.com/v3/mcp", "--header", "statsig-api-key: console-YOUR-CONSOLE-API-KEY"]

Use a Statsig Console API key with the permissions needed for the task (read-only for viewing, write for changes), created under Settings -> Keys & Environments. Do not ask the user to paste credentials into chat. Restart Codex after editing its configuration. Other clients should use their supported remote MCP setup with the same v3 URL.

For existing connections and reconnect guidance, read the MCP reference.