Bring Feature Flags
to LlamaIndex
Learn how to connect Statsig to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine Statsig tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Statsig tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Statsig tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Statsig, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Statsig tools were called, what data was returned, and how it influenced the final answer
Statsig in LlamaIndex
Statsig and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statsig to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Statsig tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
CDC WONDER (Epidemiologic Data)
1 toolsAccess public health data from the CDC WONDER system, including mortality, births, and vaccine adverse events directly through your AI agent.
Geekflare
7 toolsTest your website performance, security headers, and DNS configuration with a comprehensive suite of technical audit tools.
Odoo ERP (Full)
7 toolsManage CRM leads, contacts, companies, sales orders, and notes — complete Odoo ERP access through natural conversation.
Zoho CRM Contacts
11 toolsSearch, create, and manage contacts, leads, and accounts — with lead conversion and related records in Zoho CRM.