Feature Flag
Statsig MCP connector
Connect Statsig to Elaichi and Claude, ChatGPT, Cursor or any MCP client can list, inspect, create and update the feature gates, experiments, dynamic configs and metrics each person on your team already has access to.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Statsig to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Statsig once
-
Open Connections, choose Add connection, and pick Statsig.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Statsig. Statsig's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Statsig MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Statsig MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Statsig MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Statsig to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Statsig through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Check which gates are on before launch
Ask which feature gates are fully rolled out, which are still partial, and who they target, then read the rules without opening the Statsig console.
-
Engineering
Create a gate without leaving the editor
From Cursor, ask for a new feature gate in Statsig named for the feature you are building, with the rollout rule you want, if your Statsig role allows writes.
-
Growth
Read experiment results in plain language
Ask how an experiment is performing, which variant is ahead, and whether it has reached significance, with the answer pulled from the live experiment in Statsig.
-
Data
Inspect the metrics behind an experiment
List the metrics attached to an experiment in Statsig, check how each one is defined, and spot the ones that are missing before a readout.
-
Marketing
Update a dynamic config for a campaign
Change the copy or dates held in a dynamic config in Statsig for a promotion, and confirm what it looked like before and after.
-
Support
Explain why a customer sees a feature
Look up the feature gate that controls a feature in Statsig and read its targeting rules to tell a customer why they do or do not see it.
Try asking
- “Which feature gates are fully rolled out in production?”
- “Summarize the results of the checkout redesign experiment.”
- “Create a dynamic config for the spring pricing banner.”
Compare
Elaichi vs Zapier MCP vs Composio for Statsig
All three can connect Statsig to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Statsig tools | Allow or restrict single Statsig tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Statsig call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Statsig gets you
5 screens from the product, each doing one job for your Statsig account.
The agent
Ask plain questions, get live Statsig answers.
Elaichi's agent reads the feature gates and experiments your Statsig account already holds.
- gates
- experiments
- dynamic configs
- metrics
Ask Elaichi to work across your apps.
Which feature gates are fully rolled out in production?
Summarize the results of the checkout redesign experiment.
Create a dynamic config for the spring pricing banner.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Statsig endpoint for every AI client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Statsig toolbox.
Product, Engineering and Growth each work from a toolbox scoped to their own job.
- Product
- Engineering
- Growth
- Data
ElaichiToolboxesShared connections
Teammates work through Statsig without seeing credentials.
One person connects Statsig, shares it with teams, and nobody else handles a credential.
- Product
- Engineering
- Growth
- Data Science
ElaichiConnectionsAudit log
Every Statsig call is logged with a name.
When, who, what happened and which gate or experiment, in an append-only audit log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs Statsig work end to end.
Experiments are fetched and grouped, an agent drafts a digest, and a person approves it.
Statsig digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch gates
Statsig
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Statsig
Queued
Collections and dashboards
Statsig health numbers, computed without a model.
Four metrics, fourteen days of gates created and a breakdown by team, refreshed on schedule.
Statsig health
Refreshed 4 minutes ago · every 15 minutes · from the gates collection
Gates
1,284 ↓ 12%
Experiments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Gates created
Last 14 days
By team
Share of activity
Product 34%
Engineering 27%
Growth 21%
Data Science 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Statsig to Claude?
In Elaichi, choose Statsig and sign in with your Statsig account over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then work with your feature gates, experiments, dynamic configs and metrics.
Does Statsig work with ChatGPT and Cursor as well as Claude?
Yes. Once Statsig is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Statsig once and every client gets it.
What can an AI agent actually do with my Statsig data?
An agent can list and inspect your feature gates, experiments, dynamic configs and metrics in Statsig, and explain them in plain language. If your Statsig role allows writes, it can also create or update a gate, an experiment or a dynamic config when you ask. Short concrete asks, such as naming the gate you mean, work better than long sentences.
Does connecting Statsig give the AI access to my whole project?
No. Access follows the person who signed in to Statsig, so an agent sees only the projects, gates and experiments that person can already see, and can write only where their Statsig role allows. Elaichi can narrow that access further with restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Statsig?
Yes. In Elaichi, restrictions on the Statsig connection are set per action, so you can allow reading gates and experiments while blocking any create or update. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Statsig connection when someone leaves?
Offboarding that person in Elaichi ends their access to Statsig through every client at once. A Statsig connection shared with a team keeps working for everyone else. Disconnecting Statsig once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Statsig MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Statsig is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Statsig?
Yes. Both let Claude, ChatGPT or Cursor use Statsig. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Statsig call.
How is Elaichi different from Composio for Statsig?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Statsig: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Statsig in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.