Statsig MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Check Gate, Create Dynamic Config, Create Gate, and more
GDPR Free for SubscribersGitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this MCP Server for VS Code Copilot
The Statsig MCP Server for VS Code Copilot is a standout in the Developer Tools category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Gemini{
"mcpServers": {
"statsig": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Statsig and 4,000+ MCP Servers from a single visual interface.
* 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
About Statsig MCP Server
Connect your Statsig project to any AI agent to manage feature rollouts and product experiments through natural conversation.
GitHub Copilot Agent mode brings Statsig data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
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
The Statsig MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Statsig tools available for VS Code Copilot
When VS Code Copilot connects to Statsig through Vinkius, your AI agent gets direct access to every tool listed below — spanning feature-flags, ab-testing, product-experimentation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Check gate on Statsig
Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user
Create dynamic config on Statsig
Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config
Create gate on Statsig
Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate
Delete gate on Statsig
Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate
Get config on Statsig
Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment
Get dynamic config on Statsig
Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config
Get gate on Statsig
Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate
Get layer on Statsig
Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer
List dynamic configs on Statsig
Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project
List gates on Statsig
Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project
Log event on Statsig
Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation
Update gate on Statsig
Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate
Connect Statsig to VS Code Copilot via MCP
Follow these steps to wire Statsig into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Statsig
Why Use VS Code Copilot with the Statsig MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Statsig through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Statsig + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Statsig MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Statsig in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Statsig immediately.
"Check if the gate 'new_checkout_flow' is enabled for user 'user_99'."
"List all feature gates in my Statsig project."
"Create a new feature gate named 'mobile_redesign' with description 'Testing new UI'."
Troubleshooting Statsig MCP Server with VS Code Copilot
Common issues when connecting Statsig to VS Code Copilot through Vinkius, and how to resolve them.
MCP tools not available
Statsig + VS Code Copilot FAQ
Common questions about integrating Statsig MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.Explore More MCP Servers
View all →
Freshworks
9 toolsManage unified CRM and support via Freshworks — track sales deals and accounts, handle helpdesk tickets, and manage contacts directly from any AI agent.
Mistral AI
10 toolsAccess Mistral AI models via API — chat with Claude alternatives, generate embeddings, moderate content and manage batch jobs from any AI agent.
BoxyHQ (Enterprise SSO)
8 toolsManage Enterprise SSO and Directory Sync (SCIM) via BoxyHQ — configure SAML/OIDC connections and automate user provisioning directly from your AI agent.
Swiftype
10 toolsConnect your AI to Elastic Swiftype. Query your search engines, manage documents, and retrieve deep analytical insights natively from the terminal.