FEATURE FLAGS / Statsig
Statsig MCP Server
Statsig's hosted MCP server (V3) exposing the Console API to agents over HTTP with OAuth: 18 default tools that read gates, experiments, dynamic configs, metrics and logs, create and update gates, experiments and dynamic configs, and discover further operations. Write tools require write access, and updates and destructive operations require an explicit confirmation.
“Read-only users can connect and use all read tools. Write tools require an API key with write permissions.”
01 / THE REASONING
Why this made the selection.
- Statsig hosts the server itself at https://api.statsig.com/v3/mcp, announced in its 5 June 2025 product update, with setup guides for Codex, the ChatGPT connector, Cursor, Claude Code and manual configuration.
- The read/write split is enforced by credential: read-only users get every read tool, write tools require an API key with write permissions, and update tools and api_destructive operations also require a confirmation argument.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Statsig MCP documentation overview, read 2026-10-13: setup guides for Codex, ChatGPT connector, Cursor, Claude Code and manual setup; 18 default tools in five groups; safety and confirmation rules; V1 connections remain supported; GET and POST; read-only users can use all read tools while write tools require an API key with write permissions; the stale-gate cleanup prompt.
- Statsig Claude Code setup guide: endpoint https://api.statsig.com/v3/mcp over the HTTP transport with OAuth; OAuth only supports Personal Console API Keys, which the organisation owner must enable per role; a Console API key header as the alternative; verification is listing experiments or gates.
- Statsig manual setup guide: a generic mcpServers JSON block with the V3 URL and OAuth, for clients that support Streamable HTTP.
- Statsig product update (June 5, 2025): Statsig now hosts an MCP server acting as the bridge between AI applications and Statsig.
Our findings
- The server is vendor-hosted and remote; no official server source repository exists, so repository and revision are null per the hosted-server precedent.
- The docs include a worked stale-gate cleanup prompt that has the agent call gate_read to list STALE gates and then remove the gate checks from the code.
- The overview lists 18 default tools: get_context, search and fetch; gate_read, experiment_read, dynamic_config_read, metric_read and log_read; gate_create, experiment_create and dynamic_config_create; gate_update, experiment_update and dynamic_config_update; and discover_tools, api_read, api_write and api_destructive.
- Corrected 2026-10-13: this record said the capability set was fixed and additions came by request via Slack; the V3 overview now offers discovery tools that reach any exposed operation.
- configExample is the manual setup guide's OAuth block. Corrected 2026-10-13: the earlier example added a "type": "http" key and was attributed to the Claude Code guide, which shows commands, not JSON.
Not established by this review
- No Statsig account was connected and no gate, experiment or metric call was executed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add https://api.statsig.com/v3/mcp as an HTTP MCP server in the client (Claude Code: claude mcp add --transport http statsig https://api.statsig.com/v3/mcp).
- Run the client's MCP authentication command and authorise the server in the browser.
- Ask the assistant to list experiments or gates to verify the connection.
Before you start
- A Statsig account with access to the target project.
- For OAuth, Personal Console API Keys enabled for your role by the organisation owner.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"statsig": {
"url": "https://api.statsig.com/v3/mcp"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.statsig.com/integrations/mcp/overview
Supports: summary, upstreamDescription, descriptionSourceUrl, access, limitations, whySelected, bestFor, review
https://docs.statsig.com/integrations/mcp/claude-code
Supports: install, transports, compatibility, access
https://www.statsig.com/updates/update/mcpserver
Supports: summary, whySelected
https://docs.statsig.com/integrations/mcp/manual-setup
Supports: configExample, transports, compatibility