Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Statsig in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Drive Statsig (feature flags + experiments + analytics) from any AI agent: evaluate gates/dynamic configs/experiments, log events, manage console-side gates and experiments. 10 tools, server-secret-key auth.
Try asking
Example prompts for Statsig
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Statsig, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Statsig + Gemini
Drive Statsig (feature flags + experiments + analytics) from any AI agent: evaluate gates/dynamic configs/experiments, log events, manage console-side gates and experiments. 10 tools, server-secret-key auth.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
STATSIG_SERVER_SECRET_KEY
Step 1 — Get credentials
statsig.com).
Two distinct APIs:
- Server SDK API (
api.statsig.com/v1/...) — runtime evaluation + event logging. RequiresSTATSIG_SERVER_SECRET_KEY(starts withsecret-). - Console API (
statsigapi.net/console/v1/...) — admin operations like creating gates. RequiresSTATSIG_CONSOLE_API_KEY(starts withconsole-). The adapter uses the Server SDK base by default; tools that hit the Console API set explicit absolute URLs in their endpointMapping.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
- Save the file and restart
gemini. - Run
/mcpinside the Gemini CLI —Statsigshould be listed as available. - Vertex AI Studio: pass
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDto thetoolsarray of your request with the sameX-API-Keyheader.
Available tools
| Tool | What it does |
|---|---|
statsig_check_gate | Evaluate a feature gate (boolean flag) for a user |
statsig_get_config | Evaluate a Dynamic Config for a user |
statsig_get_experiment | Evaluate an experiment for a user |
statsig_initialize | Bulk evaluate ALL gates/configs/experiments for a user in one call |
statsig_log_event | Log a custom event for analytics + experiment exposure tracking |
statsig_list_gates | Console: list feature gates defined in the project |
statsig_get_gate_config | Console: fetch a gate's definition (rules, targeting) |
statsig_create_gate | Console: create a new feature gate |
statsig_list_experiments | Console: list experiments |
statsig_get_experiment_results | Console: fetch experiment metric results (pulse readout) |
FAQ
Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with custom headers.
Next steps
Was this guide helpful?
