4,000+ servers built on vurb.ts
Vinkius

Statsig MCP Server for Claude CodeGive Claude Code instant access to 12 tools to Check Gate, Create Dynamic Config, Create Gate, and more

MCP Inspector GDPR Free for Subscribers

Claude Code is Anthropic's agentic CLI for terminal-first development. Add Statsig as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.

Ask AI about this MCP Server for Claude Code

The Statsig MCP Server for Claude Code is a standout in the Developer Tools category — giving your AI agent 12 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·bash
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add statsig --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Statsig and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Statsig
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Statsig MCP Server

Connect your Statsig project to any AI agent to manage feature rollouts and product experiments through natural conversation.

Claude Code registers Statsig as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Statsig data drives decisions without human intervention.

What you can do

  • Feature Gates — Evaluate if a feature is enabled for a specific user or list all project gates
  • Dynamic Configs — Fetch JSON configurations and experiments to control app behavior without code changes
  • Event Logging — Log custom events for real-time analytics and metric calculation
  • Gate Management — Create, update, or delete feature gates directly via the Console API
  • Layer Inspection — Evaluate layers and retrieve parameter values for specific users

The Statsig MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Code in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Statsig tools available for Claude Code

When Claude Code connects to Statsig through Vinkius, your AI agent gets direct access to every tool listed below — spanning feature-flags, ab-testing, product-experimentation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

check

Check gate on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user

create

Create dynamic config on Statsig

Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config

create

Create gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate

delete

Delete gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate

get

Get config on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment

get

Get dynamic config on Statsig

Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config

get

Get gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate

get

Get layer on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer

list

List dynamic configs on Statsig

Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project

list

List gates on Statsig

Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project

log

Log event on Statsig

Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation

update

Update gate on Statsig

Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate

Connect Statsig to Claude Code via MCP

Follow these steps to wire Statsig into Claude Code. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
02

Add the MCP Server

Run the command above in your terminal
03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
04

Start using Statsig

Ask Claude: "Using Statsig, show me...". 12 tools are ready

Why Use Claude Code with the Statsig MCP Server

Claude Code provides unique advantages when paired with Statsig through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using Statsig tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

Statsig + Claude Code Use Cases

Practical scenarios where Claude Code combined with the Statsig MCP Server delivers measurable value.

01

CI/CD integration: embed Statsig tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query Statsig nightly and generate reports without human intervention

03

Shell scripting: pipe Statsig outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query Statsig status endpoints and alert on anomalies

Example Prompts for Statsig in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with Statsig immediately.

01

"Check if the gate 'new_checkout_flow' is enabled for user 'user_99'."

02

"List all feature gates in my Statsig project."

03

"Create a new feature gate named 'mobile_redesign' with description 'Testing new UI'."

Troubleshooting Statsig MCP Server with Claude Code

Common issues when connecting Statsig to Claude Code through Vinkius, and how to resolve them.

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Statsig + Claude Code FAQ

Common questions about integrating Statsig MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Explore More MCP Servers

View all →