# Statsig MCP server > Manage Statsig feature gates, experiments, dynamic configs and metrics from your AI assistant. - Listing: https://mcp.tc/i/statsig - Connect: use the server's own URL `https://api.statsig.com/v3/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: Statsig - Homepage: ## About Connects an assistant to your Statsig project so it can read and manage feature gates, experiments, dynamic configs, metrics and audit logs. It also has search and fetch tools, and a discovery tool that finds other operations such as layers, segments, holdouts, tags and reviews. Runs as a hosted streamable HTTP endpoint at https://api.statsig.com/v3/mcp. Sign in with OAuth, or send a Statsig Console API key in the statsig-api-key header. Create and update tools need write access, and updates and destructive operations ask for confirmation. ## What it can do - Read and inspect feature gates, experiments, dynamic configs and metrics - Create gates, experiments and dynamic configs - Update existing resources with a confirmation step - Query audit logs and Logs Explorer data - Search and fetch Statsig resources - Discover and run other API operations such as layers, segments and holdouts ## Example prompts - "List the experiments currently running in my Statsig project." - "Create a feature gate named new\_checkout with a 10 percent rollout." - "Show recent audit log entries for the gate new\_checkout." - "Find stale feature gates that could be cleaned up." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http statsig https://api.statsig.com/v3/mcp ``` 2. Start Claude Code, type `/mcp`, pick **statsig** and choose **Authenticate**. A browser window opens for the Statsig sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Statsig** and paste this URL: ```url https://api.statsig.com/v3/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Statsig asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://api.statsig.com/v3/mcp` and click **Add**. 3. Click **Connect** and sign in when Statsig asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://api.statsig.com/v3/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Statsig to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "statsig": { "url": "https://api.statsig.com/v3/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"statsig","type":"http","url":"https://api.statsig.com/v3/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "statsig": { "type": "http", "url": "https://api.statsig.com/v3/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "statsig": { "serverUrl": "https://api.statsig.com/v3/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add statsig --url https://api.statsig.com/v3/mcp codex mcp login statsig ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.statsig] url = "https://api.statsig.com/v3/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http statsig https://api.statsig.com/v3/mcp ``` Then, inside Gemini CLI, run `/mcp auth statsig` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "statsig": { "type": "http", "url": "https://api.statsig.com/v3/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.statsig.com/v3/mcp`. ## Details - Server version: 1.0.0 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/statsig (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report