VS Code CopilotIDE

ConfigCat MCP Server

Bring Feature Flags
to VS Code Copilot

Name: ConfigCat MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

Learn how to connect ConfigCat to VS Code Copilot and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Create ConfigCreate EnvironmentCreate SegmentCreate SettingDelete ConfigDelete EnvironmentDelete SegmentDelete SettingGet ConfigGet EnvironmentGet SegmentGet SettingGet Setting ValueList ConfigsList EnvironmentsList SegmentsList SettingsUpdate Setting Value

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the ConfigCat MCP Server?

Connect ConfigCat to any AI agent to streamline your feature flag management and release workflows through natural conversation.

What you can do

Configurations & Environments — List, create, and manage configuration containers and environments (Test, Staging, Production) across your products.
Feature Flags & Settings — Create and inspect feature flags or settings (boolean, string, int, double) to control application logic.
Value Management — Retrieve and update setting values dynamically to trigger real-time changes in your software without redeploying.
Segment Control — Manage user segments to target specific groups for canary releases or A/B testing.

How it works

Subscribe to this server
Enter your ConfigCat API Key ID and Secret
Start managing your feature toggles from Claude, Cursor, or any MCP-compatible client

Who is this for?

Developers — toggle features and check flag statuses directly from the code editor to maintain focus.
DevOps Engineers — manage environments and configurations as part of the CI/CD workflow via automated agents.
Product Managers — oversee feature rollouts and user segments through simple chat commands without technical overhead.

Built-in capabilities (18)

create_config

Create a new configuration

create_environment

Create a new environment

create_segment

Create a new segment

create_setting

Create a new feature flag or setting

delete_config

Delete a configuration

delete_environment

Delete an environment

delete_segment

Delete a segment

delete_setting

Delete a setting

get_config

Get details of a specific configuration

get_environment

Get details of an environment

get_segment

Get details of a segment

get_setting

Get details of a setting

get_setting_value

Get the value of a setting in an environment

list_configs

List all configurations in a product

list_environments

g., Test, Production) for a specific product. List all environments in a product

list_segments

List all segments in a product

list_settings

List all settings in a configuration

update_setting_value

Update the value/targeting of a setting

Why VS Code Copilot?

GitHub Copilot Agent mode brings ConfigCat data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 18 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

See it in action

ConfigCat in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

ConfigCat and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect ConfigCat 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for ConfigCat in VS Code Copilot

The ConfigCat 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 18 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.

Unlock for AI Agents View full ConfigCat details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures
ConfigCat for VS Code Copilot

Every tool call from VS Code Copilot to the ConfigCat MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I list all feature flags in a specific configuration?

Yes. Use the list_settings tool with your Configuration ID to retrieve all feature flags and settings, including their types and keys.

How do I create a new environment like 'Staging'?

Simply use the create_environment tool. Provide the Product ID and the name 'Staging' to instantly set up a new environment for your flags.

Is it possible to update the value of a setting remotely?

Yes! The update_setting_value tool allows you to change the value of any flag or setting for a specific environment in real-time.

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.