Skip to content

Statsig

Updated View as Markdown

Review feature gates, experiments and dynamic configuration metadata. Bring a release’s saved rollout context into your investigation.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Review launch readiness

List the first page of 20 feature gates in my connected Statsig project. Summarize each gate’s enabled state and version where returned, and identify names relevant to the checkout launch. Treat enabled state as configuration metadata, not evidence of which users receive a feature. Do not evaluate or change gates.

Explore this command: statsig.gates.list

Inspect an experiment

Read the metadata for the Statsig experiment whose ID I provide. Summarize its saved name, description, status and version where available. Identify missing context I should check before discussing the launch. Do not fetch experiment results, run analyses or change the experiment.

Explore this command: statsig.experiments.get

What you can do (6)

What you can do

Available commands: 6 (6 read, 0 write). Enable only the commands your application needs.

Command Effect
List feature gates — statsig.gates.list Read
Get feature gate — statsig.gates.get Read
List experiments — statsig.experiments.list Read
Get experiment — statsig.experiments.get Read
List dynamic configurations — statsig.dynamic-configs.list Read
Get dynamic configuration — statsig.dynamic-configs.get Read

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Statsig, then enter the issued values in the connection form below.

  1. In Statsig open Project Settings > API Keys and create a dedicated Console API key with read access to the intended project. Paste the console- key into Statsig Console API key. Client and server SDK keys cannot authorize Console API reads. Select only the required metadata commands. Lists require a limit of 1–100 and a page number. These commands do not evaluate gates, run experiments, read configuration values or change rollouts. Disconnect in Tooluse.net and revoke the key in Statsig when finished.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Statsig Console API key Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "limit": 20,
      "page": 1
    }
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

List feature gates — statsig.gates.list

List one explicit page of feature gates metadata. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.limit integer Required minimum: 1; maximum: 100
query.page integer Required minimum: 1; maximum: 10000

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "limit": 20,
    "page": 1
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Get feature gate — statsig.gates.get

Read metadata for one identified feature gate. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.id string Required minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9][A-Za-z0-9_.-]*$"

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "id": "checkout_v2"
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

List experiments — statsig.experiments.list

List one explicit page of experiments metadata. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.limit integer Required minimum: 1; maximum: 100
query.page integer Required minimum: 1; maximum: 10000

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "limit": 20,
    "page": 1
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Get experiment — statsig.experiments.get

Read metadata for one identified experiment. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.id string Required minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9][A-Za-z0-9_.-]*$"

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "id": "checkout_v2"
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

List dynamic configurations — statsig.dynamic-configs.list

List one explicit page of dynamic configurations metadata. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.limit integer Required minimum: 1; maximum: 100
query.page integer Required minimum: 1; maximum: 10000

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "limit": 20,
    "page": 1
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Get dynamic configuration — statsig.dynamic-configs.get

Read metadata for one identified dynamic configuration. No evaluation, analytics query, rollout change or automatic pagination is performed.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.id string Required minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9][A-Za-z0-9_.-]*$"

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "id": "checkout_v2"
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close