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.

Statsig MCP with Other MCP-Compatible Clients

Learn how to manually configure the Statsig MCP server for any MCP-compatible tool.

If your tool doesn't have a specific setup guide, you can manually configure the Statsig MCP server. This guide covers the general configuration steps that work with any MCP-compatible client.

Prerequisites

  • A Statsig account (sign up at console.statsig.com)
  • An MCP-compatible tool or client that supports Streamable HTTP
  • Access to your tool's configuration files

Configuration

Add the following configuration to your MCP client's configuration file:

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

This installs the Statsig MCP server with OAuth. When you first use the MCP server:

  1. Your tool prompts you to authenticate.
  2. Statsig redirects you to its OAuth page.
  3. Sign in and authorize the MCP server.
  4. Your tool stores the authentication token automatically.

MCP OAuth only supports Personal Console API Keys. Ensure your Statsig org owner has enabled Personal Console API Keys creation for your role in organization settings.

Verification

After adding the configuration:

  1. Restart your tool to apply the changes.
  2. Check your tool's MCP server list to verify Statsig appears.
  3. Try using a Statsig MCP command to test the connection.

Testing the connection

You can test the connection by asking your tool to:

  • Check the project: "Which Statsig project am I connected to, and what permissions do I have?"
  • List experiments: "Get list of experiments"
  • List gates: "Get list of gates"
  • Get details: "Get details for experiment [experiment-id]"

Was this helpful?