On this page

For AI agents: a documentation index is available at /llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

Connect Statsig to Claude

Connect Claude to your Statsig project with OAuth to inspect experiments, feature gates, and dynamic configs.

Connect the Statsig MCP server to Claude to inspect your project's experiments, feature gates, dynamic configs, and metrics from a conversation. Authorize write access to create resources and apply permitted changes.

This guide covers Claude on the web and Claude Desktop. For command-line setup, follow the Claude Code guide.

Prerequisites

  • A Claude account with permission to add a custom connector. Your Claude organization can restrict connector installation.
  • A Statsig account with access to the project you want to connect.
  • Permission to create Personal Console API Keys. Your Statsig organization owner controls this permission in organization settings.

Add the Statsig connector

  1. In Claude, open Customize > Connectors.

  2. Select Add, then choose Custom > Web.

  3. Enter Statsig as the connector name and this remote server URL:

    text
    https://api.statsig.com/v3/mcp
    
  4. Continue to the authentication settings. Choose OAuth sign-in and Use Claude's published identity for the OAuth client.

  5. Connect and sign in to Statsig. Select the project and access level you want to authorize.

  6. Return to Claude and enable the Statsig connector in a conversation.

Claude stores the connection for future conversations. If your organization manages connector installation, ask your Claude administrator to add Statsig.

Verify your project and access

Ask Claude:

text
Which Statsig project am I connected to, and what permissions do I have?

Check that the project matches your intended workspace before requesting changes. Then try a read:

text
List up to five feature gates in this project, then explain the targeting rules for one gate I select.

You can also ask Claude to list experiments, retrieve available experiment results, or inspect a dynamic config.

Make configuration changes

Read-only access supports inspection. Write access enables permitted create and update operations. Statsig applies your project permissions and review policies to connector calls.

For example, ask Claude to create a disabled gate in a test project. If the project requires a Target App, include its name in your request.

Before an update, ask Claude to read the existing configuration and show the proposed change. Review the change before confirming it. Update tools can replace a resource's definition, so preserve fields you want to keep.

Troubleshoot the connection

  • Sign-in fails: Check that your role can create Personal Console API Keys and that you have access to the selected project.
  • The project is incorrect: Reconnect Statsig and authorize the intended project before making changes.
  • Write tools are missing: Check the access level you granted and your Statsig project permissions.
  • Claude asks to approve a tool again: Review the tool's current description and arguments. A changed tool definition can require approval again.
  • The connector loads no tools: Verify that the server URL is https://api.statsig.com/v3/mcp, then reconnect.

Was this helpful?