Statsig MCP. Manage features and test product rollouts.
Statsig connects feature flagging and experimentation directly to your AI agent. Test product rollouts, manage dynamic configurations, and log custom events—all through natural conversation. Instead of writing code or jumping between dashboards, you ask your agent about a user's gate status or fetch an experiment's JSON settings immediately.
Give Claude and any AI agent real-world access
Checks if one or more feature flags are enabled for a specific user.
Creates, updates, and deletes feature gates, allowing you to control product access without code changes.
Fetches specific JSON configurations or lists all available dynamic settings for an experiment.
Retrieves parameter values from a user's layer to understand how the feature evaluation works.
Logs custom events directly for generating analytics and calculating metrics.
Ask an AI about this
Waiting for input…
What AI agents can do with Statsig: 12 Tools for Product Experimentation
These tools allow you to manage every part of the product experimentation lifecycle—from creating a flag to logging the final event.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Statsig MCPCheck Gate
Evaluates if one or more feature gates are enabled for a specific user.
Create Dynamic Config
Creates an entirely new dynamic configuration within the Statsig project.
Create Gate
Establishes a brand-new feature gate for use in product rollouts.
Delete Gate
Removes an existing, unused feature gate from the project entirely.
Get Config
Fetches configuration values for a specific dynamic config or experiment type.
Get Dynamic Config
Reads and returns the details of an existing dynamic configuration.
Get Gate
Retrieves all information about a specific, named feature gate.
Get Layer
Fetches parameter values from a user's layer to show how the evaluation works for...
List Dynamic Configs
Provides an index of every dynamic configuration currently set up in your project.
List Gates
Lists all feature gates that exist within the current Statsig project.
Log Event
Logs custom events, allowing you to track specific user actions for analytics...
Update Gate
Modifies the settings or description of an existing feature gate.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Statsig, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Statsig. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The pain of manually checking feature flags across multiple dashboards
Right now, if you want to know if a new payment method is enabled for your test user, you have to open the Statsig UI. Then, you might need to jump to a different dashboard to view the related dynamic config, and then check another system just to confirm which layer parameters are active. It's a painful sequence of tabs and copy-pasting.
With this MCP, you simply ask your agent about it. You don't click anything. You tell it what user and what feature flag you're checking, and the agent returns the status—true or false—in one simple reply.
Statsig MCP: Instant Feature Flag Status Checks
Manual processes involve writing a small script just to run `check_gate` for every test user. Then, you have to manually read the results and cross-reference them with other internal systems.
Now, your agent handles that entire process. It performs the evaluation logic instantly through natural language conversation. You get immediate answers on feature availability without writing a single line of boilerplate code.
What Statsig MCP does for your AI
Managing feature flags used to mean living in a separate UI for every single check. Now, you can talk to your AI client and have it handle the complexity of product experimentation. Ask your agent if 'dark_mode_v2' is enabled for user 123, or ask it to fetch the configuration values for an active experiment.
You don't need to remember which API key goes where; you just describe what you want done.
This MCP lets developers and PMs verify evaluation logic right from their chat window. Need to create a new feature flag? Just tell your agent, and it handles the setup using its management tools. If you spot an interesting metric during testing, simply ask your agent to log a custom event for real-time analytics.
Because Vinkius hosts this MCP, connecting it is easy—you link once from any compatible client, and suddenly, product experimentation is just another conversation.
019e38f3-2cec-7239-aaa7-da3df1e2b898 How to set up Statsig MCP
The bottom line is you talk to your AI client about product logic, and it handles all the API calls behind the scenes.
First, subscribe to this MCP in Vinkius and provide your Statsig Server Secret Key and Console API Key.
Next, tell your agent the exact task you need—for instance, 'List all feature gates' or 'Check gate X for user Y'.
Your agent executes the request through the tools, pulling back structured data (like True/False status or JSON configs) directly into the chat.
Who uses Statsig MCP
This MCP is for Product Managers who hate waiting on engineering tickets for a simple flag check. It's for Developers tired of switching between their IDE and a dozen different dashboard tabs just to test an endpoint. And it’s perfect for Data Scientists needing quick access to configuration layers.
Verifies if a new checkout flow is ready by checking gate statuses or creating temporary feature flags without bothering engineering.
Validates evaluation logic or logs test events directly from the IDE to confirm how code interacts with dynamic configs.
Inspects experiment configurations and retrieves layer parameters to verify metric logging before running a full analysis pipeline.
Benefits of connecting Statsig MCP
You can check a user's access status immediately. Instead of navigating to the Statsig UI, asking your agent to run check_gate tells you instantly if 'new_checkout_flow' is active for that specific user.
Product changes are controlled directly via chat. Use create_gate or update_gate to manage feature flags and gates without needing a developer pull request just to flip a switch.
Configuration data comes straight to your agent. If you need the settings for an experiment, calling get_config pulls the JSON structure so your workflow can consume it instantly.
Monitoring happens in conversation. Use log_event when testing to send custom events that feed into your analytics dashboard, keeping track of every action without extra logging code.
You can build out a complete picture of user behavior. By using get_layer, you inspect the underlying parameters, which helps data scientists validate if their metric collection is working correctly.
Statsig MCP use cases
Validating an A/B Test for Marketing
A Product Manager needs to know if a new landing page variant ('redesign') is live. They ask the agent, 'What's the status of the redesign gate for user X?' The agent runs check_gate and confirms its status (True/False), letting them greenlight the launch immediately.
Debugging a Broken Feature in Code
A Developer finds a bug related to settings. They ask the agent to fetch the configuration for 'payment_gateway' using get_dynamic_config. This returns the exact JSON they need, letting them fix the issue without searching through old documentation.
Tracking User Funnel Drop-off Points
A Data Scientist suspects a specific user action is failing. They ask the agent to log_event when that failure point is hit, tagging it with context. This creates a clean data stream for metric calculation.
Onboarding a New Team Member
A new PM needs to see all available features for the project. They ask the agent to list_gates, which instantly provides them with a comprehensive list of every flag and gate that exists, letting them start planning right away.
Statsig MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to manage all data in one place
Copying configuration values from the Statsig web console and pasting them into a spreadsheet or another database tool.
Instead, use your agent. If you need the config, ask it to get_dynamic_config or get_config. It pulls structured data directly into your chat window for immediate consumption.
Hardcoding feature logic in client code
Writing an 'if (user.isPremium)' check every time a developer builds a new screen, which requires full redeployment.
Use the MCP to manage this instead. Just ask your agent to create_gate and control access via feature flags, letting you roll out changes without touching the code base.
Forgetting to track key user actions
Not logging when a critical button is clicked in testing because it's not part of the core flow.
Use log_event. You can easily instruct your agent to log custom events anytime, ensuring every metric you care about gets tracked for analytics.
When to use Statsig MCP
Use this MCP if your team needs to test product hypotheses and manage features dynamically. This is the tool for controlling access, running A/B tests, and verifying configurations without code changes. You absolutely need it if Product Managers or Developers need immediate answers on gate status (using check_gate) or need to log custom events (log_event) during development.
Don't use this MCP if you simply need general API access—like reading a public list of users, or managing unrelated infrastructure resources. For pure data storage and retrieval that has nothing to do with product feature toggles, look for dedicated database connectors instead. This is highly specialized for the product experimentation lifecycle.
Frequently asked questions about Statsig MCP
How do I use Statsig MCP to check if a gate is active? +
You ask your agent to run the check_gate tool and provide the specific feature name and user ID. The agent evaluates the flag using the secret key and tells you the status (True/False).
Can I use Statsig MCP to create new features? +
Yes, you can manage your flags directly. Use create_gate or update_gate when you need to establish a feature flag or modify an existing one's settings.
What is the difference between dynamic configs and gates in Statsig MCP? +
Gates control whether a feature can be used at all. Dynamic configs store flexible data, like API keys or UI colors, that the feature uses once it's active.
If I need to track user actions, which tool do I use in Statsig MCP? +
You use log_event. This tool lets you send custom events for analytics. You tell the agent what action happened and when it occurred.
Does Statsig MCP require specific keys to run? +
Yes, the setup requires your Statsig Server Secret Key for evaluation tools (like check_gate) and your Console API Key for management tasks (like create_gate).