MCP.so
Sign In

Statsig

@statsig-io

About Statsig

Bridges directly to Statsig, enabling you to wrap new features behind feature flags, add instrumentation for product performance visibility, and seamlessly highlight and clean up stale feature flags from your codebase.

Basic information

Category

Other

Transports

stdio

Publisher

statsig-io

Submitted by

helen-statsig

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "statsig-local": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.statsig.com/v1/mcp",
        "--header",
        "statsig-api-key:${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "<console-YOUR-API-KEY>"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Statsig?

Statsig is an MCP server that implements the Model Context Protocol for integration with the Statsig API, supporting both stdio and SSE transports.

How to use Statsig?

Install with npm install and npm run build, then configure an MCP client by adding an entry to mcp.json using npx mcp-remote with the Statsig MCP endpoint URL and a statsig-api-key header supplied via the AUTH_TOKEN environment variable.

Key features of Statsig

  • MCP integration with the Statsig API
  • Supports stdio and SSE transports
  • Uses API key authentication via header

Use cases of Statsig

FAQ from Statsig

What transport protocols does Statsig support?

The server supports both stdio and SSE transports.

What authentication does Statsig require?

It uses a statsig-api-key header, with the key provided through the AUTH_TOKEN environment variable.

How is Statsig installed and built?

Run npm install followed by npm run build.

Is there any example configuration for an MCP client?

Yes, the README shows a mcp.json example using npx mcp-remote with the endpoint URL and header.

Comments

More Other MCP servers