---
title: "Statsig MCP with Other MCP-Compatible Clients"
description: "Learn how to manually configure the Statsig MCP server for any MCP-compatible tool."
product: general
token_estimate: 726
---
# Statsig MCP with Other MCP-Compatible Clients

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

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](https://console.statsig.com))
- An MCP-compatible tool or client
- 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/v1/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

> **Note:**
>
> 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](https://console.statsig.com/settings?tab=organization){" "}

#### Using API Key instead of OAuth

OAuth is the recommended setup, but you can also authenticate with your Console API key. Add the below configuration to your MCP client's configuration file:

```json
{
  "mcpServers": {
    "statsig": {
      "command": "npx mcp-remote https://api.statsig.com/v1/mcp --header statsig-api-key:${AUTH_TOKEN}",
      "env": {
        "AUTH_TOKEN": "console-YOUR-CONSOLE-API-KEY"
      }
    }
  }
}
```

Replace `console-YOUR-CONSOLE-API-KEY` with your actual Statsig Console API key, which you can retrieve from the [API keys page](https://console.statsig.com/api_keys). Ensure your API key has the right permissions: read-only keys can view data, while write keys can make changes to your project.

## 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:

- **List experiments**: "Get list of experiments"
- **List gates**: "Get list of gates"
- **Get details**: "Get details for experiment \[experiment-id\]"

## Next steps

- [MCP capabilities](https://docs.statsig.com/integrations/mcp/overview#current-mcp-capabilities)
- [Use cases](https://docs.statsig.com/integrations/mcp/overview#use-cases) for Statsig MCP
- Tool-specific guides: [Cursor](https://docs.statsig.com/integrations/mcp/cursor), [Claude Code](https://docs.statsig.com/integrations/mcp/claude-code), [Codex CLI](https://docs.statsig.com/integrations/mcp/codex)