Migrate to Statsig MCP V3

Statsig MCP V3 replaces the 93 individual tools on the V1 server with 18 default tools and a discovery layer. Statsig recommends V3, but V1 remains supported, so you can migrate when you're ready. Use this page to find the V3 replacement for each V1 tool you use and update your prompts, scripts, and automation.

Prerequisites

• An existing Statsig MCP connection that uses the V1 server URL (https://api.statsig.com/v1/mcp)
• A V3 connection (https://api.statsig.com/v3/mcp). Follow the manual setup or your client's setup guide.

How the mapping works

Each V1 tool maps to one of two V3 calls.

Direct call: Call the named V3 tool.

• For grouped read tools such as gate_read, set action to the listed action and put the V1 argument object under arguments.params.
• Create tools take the body in params["application/json"].
• Update tools require arguments.params and confirmation.
• get_context, search, fetch, and discover_tools use their own schemas.

Discovery call: Rows that start with "Discovery" take two steps:

1. Call discover_tools with action set to get and the listed operation ID.
2. Call the execution tool the response returns (api_read, api_write, or api_destructive) with its operationHandle and arguments that match the returned schema. Include confirmation when the schema requires it.

An operationHandle expires, so retrieve a new one when you need it instead of hardcoding it. api_destructive also covers some updates and review actions, not only deletion. Your project permissions and review policies still apply.

Example: read a gate

To replace Get_Gate_Details_by_ID, call gate_read:

{
  "action": "get_gate_details_by_id",
  "arguments": {
    "params": { "path_id": "your_gate_id" }
  }
}

Before you migrate

• Check the server's current tool and discovery schemas for required fields and available operations.
• For Parameter Store lookup, update, and delete, use params.path_id instead of params.path_name.
• V3 returns structuredContent alongside text. Check any response parsing in your automation.
• If you keep both versions connected while you test, disable the version you aren't testing to avoid duplicate tools.

The tool mapping covers the default V3 connection. Clients that use expanded tool exposure might also show typed tools for some discovery operations. Refer to the Statsig MCP tool reference.

Tool mapping

Context, search, and discovery

Feature gates

Experiments

Dynamic configs

Autotunes

Layers

Metrics and logs

Parameter stores

Prompts

Segments and tags