Bring Feature Flags
to VS Code Copilot
Learn how to connect Flagsmith to VS Code Copilot and start using 8 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 Flagsmith MCP Server?
Connect your Flagsmith account to any AI agent to control feature releases and remote configurations through natural conversation.
What you can do
- Flag Management — Retrieve default flag states and remote configuration values for any environment instantly.
- Identity Control — Fetch specific flags and traits for user identities or identify new users with custom traits to test personalized experiences.
- Environment Admin — Create new environments within projects and fetch full configuration documents for local evaluation modes.
- Dynamic Updates — Update flag values (single or batch) and manage segment overrides using the Admin API for rapid iteration.
- Local Evaluation — Access the entire environment configuration document for high-performance SDK integrations.
How it works
- Subscribe to this server
- Enter your Flagsmith Environment Key or Admin API Key
- Start managing your feature lifecycle from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — check flag states and user traits directly from the code editor to debug feature logic without switching contexts.
- Product Managers — toggle features, manage rollouts, and update remote configs without touching the dashboard.
- DevOps & SREs — automate environment creation and manage segment overrides through simple natural language commands.
Built-in capabilities (8)
Requires FLAGSMITH_API_KEY. Create a new environment within a project
Requires FLAGSMITH_API_KEY. Delete a segment override
Requires FLAGSMITH_ENVIRONMENT_KEY. Get the entire environment configuration document
Requires FLAGSMITH_ENVIRONMENT_KEY. Get all default flag states for an environment
Requires FLAGSMITH_ENVIRONMENT_KEY. Get flags and traits for a specific user identity
Requires FLAGSMITH_ENVIRONMENT_KEY. Identify user and set traits
Requires FLAGSMITH_API_KEY. Update a flag value (Single change)
Requires FLAGSMITH_API_KEY. Update flags (Batch change)
Why VS Code Copilot?
GitHub Copilot Agent mode brings Flagsmith data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Flagsmith in VS Code Copilot
Flagsmith and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Flagsmith to VS Code Copilot 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 Flagsmith in VS Code Copilot
The Flagsmith 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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
Flagsmith for VS Code Copilot
Every tool call from VS Code Copilot to the Flagsmith MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I retrieve flags for a specific user identity?
Yes. Use the get_identity_flags tool by providing the user's identifier. The agent will return all flags and traits associated with that specific identity in the environment.
How do I update multiple feature flags at once?
You can use the update_flag_v2 tool for batch changes. Provide the environment key and a JSON payload containing the updates you wish to apply simultaneously.
Is it possible to create a new environment via the agent?
Yes, using the create_environment tool. You will need to provide a name for the environment and the target Project ID. This requires a valid Flagsmith Admin API Key.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Wizehire
12 toolsManage candidates, job postings, and hiring stages via Wizehire directly from your AI agent.
Lemlist
8 toolsEquip your AI agent with direct access to Lemlist — manage cold email campaigns, track lead engagement, and automate outreach without opening the Lemlist dashboard.
Greenhouse
12 toolsManage your recruiting pipeline via Greenhouse — list candidates, track applications, and audit jobs directly via AI.
Withings
10 toolsAccess comprehensive health and fitness data — track weight, blood pressure, sleep cycles, steps, workouts, and heart rate directly from Withings devices.