Skip to main content

Statsig MCP

The Statsig Model Context Protocol (MCP) server lets AI tools work with your Statsig project: feature gates, experiments, dynamic configs, layers, segments, metrics, and audit logs. Connect through Cequence AI Gateway so agents can read console data and—when your credentials allow—apply updates through the same tools.

Overview​

Statsig MCP is a remote, vendor-hosted server. Statsig operates the endpoint; you point Cequence AI Gateway at their URL.

  • Server URL: https://api.statsig.com/v1/mcp
  • Transport: HTTP (streamable HTTP)
  • Hosted by: Statsig

Capabilities and behavior are defined by Statsig and may change over time. For the canonical tool list and behavior, see Statsig MCP overview.

Supported authentication types​

TypeSupportedNotes
OAuth 2YesRecommended for MCP OAuth. Statsig supports Dynamic Client Registration (DCR), so clients can complete authorization without you registering a custom OAuth client in advance.
Console API key (header)YesSome clients use mcp-remote with a statsig-api-key header and a Console API key. Read-only vs write access follows key permissions. Gateway flows typically use OAuth instead.

MCP OAuth and Personal Console API Keys​

Statsig states that MCP OAuth only supports Personal Console API Keys. Your organization must allow users in your role to create Personal Console API Keys. Org owners can configure this under Organization settings in the Statsig console (organization settings).

If OAuth is blocked by policy, use a Console API key with the appropriate scopes (read-only for queries; write keys for create/update tools), subject to your security standards.

What you can do with this MCP server​

The server exposes tools across several areas (names and parameters match Statsig’s MCP implementation):

  • Audit logs — List audit logs with filters such as id, tags, and date range.
  • Dynamic configs — Create configs, list them (e.g. by creator or tags), fetch details by ID, and replace a config entirely.
  • Experiments — Create and update experiments, list with filters (status, creator, tags, stale), fetch details, and retrieve Pulse-style results (overall and metric-by-dimension), with options such as date, CUPED, and confidence.
  • Gates (feature flags) — Create and update gates, list with filters (type, creator, tags), fetch details, and retrieve gate results/Pulse metrics.
  • Layers — Create, list, fetch by ID, and fully update layers.
  • Metrics — List metric sources, list metrics (including filters and hidden metrics), and fetch metric definitions by ID.
  • Segments — Create segments (including id list, rule-based, analysis list, and user-store id list types), list, fetch details, and update segments (rules and ID lists).

Statsig documents both read and write operations: tools can issue GET and POST requests, so updates are possible when the authenticated principal has write permission.

Prerequisites​

Before adding Statsig MCP in Cequence AI Gateway:

  • Access to Cequence AI Gateway at aigateway.cequence.ai
  • A Statsig account and access to the project you want the AI tools to use
  • For OAuth: Personal Console API Keys enabled for your role in the Statsig organization (see above)
  • For API key flows (non-gateway clients): a Console API key from API keys with suitable read/write scopes

Example workflows​

  • “List experiments that are active and summarize what each is measuring.”
  • “Show stale feature gates and help plan cleanup in our codebase.”
  • “Get Pulse results for a specific gate (by gate ID) with default CUPED and confidence settings.”
  • “Create a segment or experiment draft and outline targeting before we ship it in the console.”
  • “Pull audit log entries from last week tagged for config changes.”

Connecting MCP server from Cequence AI Gateway​

  1. Log in to Cequence AI Gateway.
  2. Choose your tenant.
  3. Go to App catalogue.
  4. Filter by Remote MCP server.
  5. Search for Statsig MCP and select it.
  6. Select Create MCP server.
  7. Choose OAuth when prompted (DCR is supported; you usually do not need a pre-registered OAuth client in Statsig).
  8. Complete the setup, select tools, and deploy.

Use the generated MCP server URL in your client as described in the Client Configuration docs. For detailed UI steps and screenshots, see Create a third-party MCP Server.

Additional information​