ConfigCat MCP Server for VS Code CopilotGive VS Code Copilot instant access to 18 tools to Create Config, Create Environment, Create Segment, and more

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

GDPR Free for Subscribers

GitHub 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

Open in ChatGPT Open in Claude Open in Perplexity

The ConfigCat MCP Server for VS Code Copilot is a standout in the Ship It category — giving your AI agent 18 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "configcat": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install ConfigCat and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

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

About ConfigCat MCP Server

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

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.

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.

The ConfigCat MCP Server exposes 18 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 18 ConfigCat tools available for VS Code Copilot

When VS Code Copilot connects to ConfigCat through Vinkius, your AI agent gets direct access to every tool listed below — spanning feature-flags, remote-config, release-management, 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.

create

Create config on ConfigCat

Create a new configuration

create

Create environment on ConfigCat

Create a new environment

create

Create segment on ConfigCat

Create a new segment

create

Create setting on ConfigCat

Create a new feature flag or setting

delete

Delete config on ConfigCat

Delete a configuration

delete

Delete environment on ConfigCat

Delete an environment

delete

Delete segment on ConfigCat

Delete a segment

delete

Delete setting on ConfigCat

Delete a setting

get

Get config on ConfigCat

Get details of a specific configuration

get

Get environment on ConfigCat

Get details of an environment

get

Get segment on ConfigCat

Get details of a segment

get

Get setting on ConfigCat

Get details of a setting

get

Get setting value on ConfigCat

Get the value of a setting in an environment

list

List configs on ConfigCat

List all configurations in a product

list

List environments on ConfigCat

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

list

List segments on ConfigCat

List all segments in a product

list

List settings on ConfigCat

List all settings in a configuration

update

Update setting value on ConfigCat

Update the value/targeting of a setting

Connect ConfigCat to VS Code Copilot via MCP

Follow these steps to wire ConfigCat into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using ConfigCat

Ask Copilot: "Using ConfigCat, help me...". 18 tools available

Why Use VS Code Copilot with the ConfigCat MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with ConfigCat 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

ConfigCat + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the ConfigCat 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 ConfigCat in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with ConfigCat immediately.

"List all configurations for product ID 'prod_123'."

"Create a new boolean feature flag called 'Beta Feature' in config 'conf_abc'."

"Show me the details for environment 'env_987'."

Troubleshooting ConfigCat MCP Server with VS Code Copilot

Common issues when connecting ConfigCat to VS Code Copilot through Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

ConfigCat + VS Code Copilot FAQ

Common questions about integrating ConfigCat MCP Server with VS Code Copilot.

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.