Statsig MCP server

The Statsig MCP Server implements the Model Context Protocol for integrating with Statsig's API services. It supports both stdio and Server-Sent Events (SSE) transport methods, making it flexible for different client environments.

Installation

To get started with the Statsig MCP Server, follow these simple installation steps:

npm install
npm run build

Usage

Configuring with MCP Client

You'll need to configure your MCP client to connect to the Statsig server by setting up the appropriate transport method in your mcp.json file.

Using stdio Transport (Default)

For the standard stdio transport method, configure your mcp.json file as follows:

{
  "mcpServers": {
    "Statsig": {
      "command": "node /path/to/build/index.js",
      "env": {
        "STATSIG_API_KEY": "console-YOUR-CONSOLE-KEY"
      }
    }
  }
}

Make sure to replace "console-YOUR-CONSOLE-KEY" with your actual Statsig console API key.

Using SSE Transport

For Server-Sent Events (SSE) transport, use this configuration:

{
  "mcpServers": {
    "Statsig": {
      "url": "http://localhost:3000/sse?STATSIG_API_KEY=console-<your-console-key>"
    }
  }
}

Security Note: When using SSE transport, be aware that some clients (like Cursor) don't currently support headers. This server accepts the Statsig API key in query parameters as a workaround. While HTTPS encryption helps protect this data in transit, it's recommended to use this method with caution in production environments.

Remember to replace <your-console-key> with your actual Statsig console API key in the URL.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "Statsig" '{"command":"node /path/to/build/index.js","env":{"STATSIG_API_KEY":"console-YOUR-CONSOLE-KEY"}}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "Statsig": {
            "command": "node /path/to/build/index.js",
            "env": {
                "STATSIG_API_KEY": "console-YOUR-CONSOLE-KEY"
            }
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "Statsig": {
            "command": "node /path/to/build/index.js",
            "env": {
                "STATSIG_API_KEY": "console-YOUR-CONSOLE-KEY"
            }
        }
    }
}

3. Restart Claude Desktop for the changes to take effect