Integrate Statsig with Claude, Cursor, Chatbots & AI Agents MCP Server

Q: What is the difference between the Server Secret Key and the Console API Key?

The Server Secret Key is used for evaluation tools like checkgate and getconfig. The Console API Key is required for management actions like listgates or creategate.

Manage feature flags, dynamic configs, and experiments. Evaluate gates and log events directly from your AI agent.

GDPR Free for Subscribers

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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

Security & Code Integrity Audit

Every tool in the Statsig MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

FScore: 3.11

How Vinkius protects your data

Can I set different limits for each virtual assistant on my team?

Absolutely. You have full control in our command center. You can create an AI agent that only "reads" data so the support team can answer questions, and another superpowered agent that can "edit" and "create" information exclusively for your operations team. Each AI gets exactly the level of access you allow.

Can I audit what my AI agents are doing with this integration?

Yes, Vinkius provides an immutable, HMAC-chained audit log. Every tool execution, payload, and response is tracked in real-time on your dashboard, giving you complete visibility into your agent's actions.

Does the AI train on my tools or API data?

No. Vinkius enforces a strict Zero-Retention policy. Your data simply passes through our secure servers to complete the requested action and is instantly forgotten. Nothing you do here is ever stored, logged, or used to train any artificial intelligence.

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.

Triggering Statsig via Natural Language

Securely interface Claude Code, ChatGPT, and Cursor with the Statsig API through semantic routing and standardized natural language triggers.

Autonomous feature flags Strategies

Provide Claude Code and Cursor with read and write access to feature flags. The Statsig toolkit handles all necessary routing for developer tools integrations.

Secure ab testing Access for Agents

Integrate the Statsig server to handle ab testing requests natively. It provides the schemas required for ChatGPT and Cursor to manage developer tools data.