Skip to content

Summary

Statsig's official remote MCP server: 80+ tools for feature gates, experiments, dynamic configs, metrics and audit logs, with reads open and writes gated on key permissions.

Features

  • 80+ tools across experiments, gates, dynamic configs, layers, segments and parameter stores
  • Experiment and gate results analysis with dimensional breakdowns and version history
  • Metric definitions, metric sources, audit logs and review workflows
  • Raw event queries and log-pattern clustering
  • Reads open to any key; writes require a Console API key with write permissions

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Statsig" tools will be available.
{
  "mcpServers": {
    "statsig-mcp": {
      "command": "claude",
      "args": [
        "mcp",
        "add",
        "--transport",
        "http",
        "statsig",
        "https://api.statsig.com/v1/mcp",
        "--header",
        "statsig-api-key: <YOUR_CONSOLE_API_KEY>"
      ]
    }
  }
}

Description

Statsig is a product-development platform combining feature management, experimentation, product analytics and session replay. Its official MCP server hands an agent 80+ tools over that data, which turns questions that normally mean clicking through a console into something you ask in the editor.

The coverage is broad. Experiments support creation, detail retrieval, results analysis with dimensional breakdowns, config updates and version history. Feature gates get full CRUD plus results analysis and the ability to kick off code cleanup once a flag is fully rolled out. Dynamic configs, layers, segments and parameter stores are all readable and writable, autotunes cover multi-armed-bandit experiments, and there are tools for metric definitions and metric sources, audit-log filtering, review workflows for gates and experiments, and querying raw events and clustered log patterns.

Authorisation follows the key you connect with: read-only users get every read tool; write operations require a Console API key with write permissions, so an agent can be given analysis access without the ability to flip a flag in production.

One detail worth knowing before you wire it up: Get_Experiment_Details_by_ID takes optional field filters that Statsig documents as cutting context consumption by 95–99%. Experiment payloads are large, and an agent that pulls them unfiltered will burn its window on metadata it does not need.

The server is remote — https://api.statsig.com/v1/mcp over streamable HTTP with a statsig-api-key header — and Statsig publishes setup guides for Claude Code, Cursor, Codex (desktop, CLI and IDE), the ChatGPT connector, and manual configuration for anything else that speaks MCP.

Related MCP Servers

New

Replicate's official MCP server: search thousands of hosted models, read their schemas, and run predictions on image, video, audio and language models from inside an agent.

MCP: Hugging Face

by Hugging Face

New

Hugging Face's official remote MCP server — search and inspect models, datasets and Spaces, browse the Hub filesystem over hf:// URIs, and turn Gradio Spaces into callable tools.

MCP: Resend

by Resend

New

Resend's official MCP server for transactional and marketing email — send, schedule and batch messages, manage templates, contacts, broadcasts, automations, domains and suppressions from an agent.

New

Postman's official MCP server — reach your workspaces, collections, specs and environments from Claude Code, Cursor, VS Code or Copilot, in four tool tiers.

Browse all MCP servers →