Statsig Mcp Server
Manage Statsig feature flags, experiments, and console analytics from your agent without leaving the IDE.
Overview
Statsig MCP Server is an MCP server for the Ship phase that lets agents interact with Statsig feature flags, experiments, and analytics via the Console API.
What is this MCP server?
- Streamable-http remote MCP at https://api.statsig.com/v1/mcp
- Requires Statsig Console API key via statsig-api-key header
- Interact with feature flags, experiments, and Statsig analytics from the API surface
- Fits agent-driven ops on an existing Statsig project—not a greenfield analytics stack
- Remote endpoint: https://api.statsig.com/v1/mcp
- Required header: statsig-api-key (Statsig Console API key)
- MCP manifest version 1.0.0
What problem does it solve?
Toggling flags and checking experiments from the IDE means context-switching to the Statsig console or writing one-off API scripts.
Who is it for?
Solo builders shipping SaaS with Statsig already wired in who want agent-assisted flag and experiment operations.
Skip if: Greenfield projects with no Statsig account, or teams that refuse to grant console API keys to agent tooling.
What do I get? / Deliverables
After registering the remote MCP with your Console API key, your agent can query and drive Statsig resources in line with your launch and rollout workflow.
- Agent-readable Statsig flag and experiment state
- Faster console API operations from the coding workflow
- Launch-time toggles and checks without leaving the agent session
Recommended MCP Servers
Journey fit
Feature flags and experiments are how solo builders ship safely and toggle launch behavior without redeploying everything. Launch subphase covers controlled rollouts, gates, and experiment reads right before and after users see the product.
How it compares
Statsig Console API MCP, not open macro data (SOTW) or qualitative market research (Aim).
Common Questions / FAQ
Who is Statsig MCP Server for?
Developers using Statsig for feature gates and experiments who want Claude Code, Cursor, or similar agents to call the Console API safely.
When should I use Statsig MCP Server?
Use it during ship and launch when you are rolling out features, inspecting experiments, or need analytics context while coding or reviewing.
How do I add Statsig MCP Server to my agent?
Add remote MCP https://api.statsig.com/v1/mcp and supply your Statsig Console API key in the statsig-api-key header per Statsig’s MCP documentation.