Bring Feature Flags
to Claude Code
Learn how to connect Statsig to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Statsig MCP Server?
Connect your Statsig project to any AI agent to manage feature rollouts and product experiments through natural conversation.
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
How it works
- Subscribe to this server
- Enter your Statsig Server Secret Key (for evaluation) and Console API Key (for management)
- Start managing your product experiments from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers — check gate statuses and create new feature flags without leaving the chat
- Developers — verify evaluation logic and log test events directly from the IDE
- Data Scientists — inspect experiment configurations and verify metric logging
Built-in capabilities (12)
Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user
Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config
Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate
Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate
Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment
Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config
Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate
Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer
Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project
Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project
Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation
Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate
Why Claude Code?
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.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Statsig tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Statsig in Claude Code
Statsig and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statsig to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Statsig in Claude Code
The Statsig 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Statsig for Claude Code
Every tool call from Claude Code to the Statsig MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is the difference between the Server Secret Key and the Console API Key?
The Server Secret Key is used for evaluation tools like check_gate and get_config. The Console API Key is required for management actions like list_gates or create_gate.
How do I evaluate a gate for a specific user?
Use the check_gate tool. You must provide the gateName and a user JSON object containing at least a userID (e.g., {"userID": "123"}).
Can I log custom events for analytics?
Yes, use the log_event tool to send an array of event objects including name, value, and user metadata to Statsig for real-time metric calculation.
How do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
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.
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.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
Mail Blaze
9 toolsManage email marketing campaigns and subscriber lists via the Mail Blaze REST API.
Mistral AI
10 toolsBuild with European open-weight language models that deliver strong reasoning, multilingual capability, and efficient inference.
Semgrep
10 toolsEquip your AI agent with read/write access to Semgrep's SAST platform to audit code security findings, update triage statuses, and enforce custom semantic rules.
Together AI
7 toolsGenerate code, evaluate embeddings, and deploy open-source LLMs instantly from your local agent via Together AI's infrastructure.