Statsig MCP server for Claude, Codex and Cursor

What your AI apps can do with Statsig

Inspect and update feature gates
Review experiments and results

Statsig MCP tools

27 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`get_context`	Returns project, permission, review and product context
`search`	Finds Statsig resources by type or target
`fetch`	Retrieves a resource chosen from search results
`gate_read`	Lists, gets and inspects feature gates and their history (read-only)
`experiment_read`	Lists and inspects experiments and pulls their results (read-only)
`dynamic_config_read`	Lists and inspects dynamic configs and their history (read-only)
`metric_read`	Lists and inspects metrics and metric sources (read-only)
`log_read`	Queries Logs Explorer and shows audit and change history (read-only)
`layer_read`	Shows layer details, experiments, overrides and lists (read-only)
`segment_read`	Lists segments or gets one by ID (read-only)
`param_store_read`	Lists parameter stores or gets their details (read-only)
`gate_create`	Create a feature gate
`experiment_create`	Create an experiment
`dynamic_config_create`	Create a dynamic config
`layer_create`	Create a layer
`segment_create`	Create a segment
`param_store_create`	Create a parameter store
`autotune_create`	Create an Autotune; requires confirmation
`gate_update`	Update a feature gate; requires confirmation
`experiment_update`	Update an experiment; requires confirmation
`dynamic_config_update`	Update a dynamic config; requires confirmation
`segment_update`	Update a segment; requires confirmation
`param_store_update`	Update a parameter store; requires confirmation
`discover_tools`	Finds additional operations and their contracts (read-only)
`api_read`	Runs a discovered read operation (read-only)
`api_write`	Runs a discovered write operation
`api_destructive`	Runs a discovered sensitive or review operation; requires confirmation (marked destructive)

Suggested access for each AI app

The documentation this list comes from doesn't mark Statsig's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Statsig connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Statsig to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Statsig tool, give Cursor only the read tools, or keep Statsig away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Statsig MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Statsig in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Statsig endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http statsig 'https://api.statsig.com/v1/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "statsig": {
      "url": "https://api.statsig.com/v1/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Statsig MCP documentation for what your client needs.

Before you connect

A Statsig account. Sign-in uses your Statsig permissions.

Server details

Detail	Value
Publisher	Statsig
Endpoint	`https://api.statsig.com/v1/mcp`
Authentication	Browser sign-in
Categories	Development
Tool list	27 tools, observed 29 October 2026 (docs)

Statsig MCP documentation