ConfigCat MCP Server for Feature Flag Management

Overview

The ConfigCat MCP (Model Context Protocol) server is a small bridge that exposes ConfigCat’s public Management API in a way that code editors and other developer tools can consume. By running the MCP server locally (or as a development integration), editors can query and operate on feature flags, configs, environments, members and other ConfigCat entities with editor-aware tooling: completions, in-code flag creation, and one-click SDK integration.

This is particularly useful when you want an editor or AI assistant to be aware of your feature flags and create or update them without context switching to the ConfigCat web UI. The MCP server supports the full range of CRUD operations available in the public management API while translating them into a set of tools/UI-friendly endpoints suitable for editor integrations.

Features

• Full CRUD access to ConfigCat Management API entities:
  • Feature flags, configs, environments, segments, products, SDK keys
• Editor integration support:
  • Provide code completions, examples and in-code flag creation flows
• Management operations for membership and permission groups
• Webhook and integration management
• Audit log and diagnostic access for compliance and traceability
• Lightweight run-mode via npx for easy local use in editors and desktop assistants

Installation / Configuration

Required environment variables:

Run the MCP server directly with npx:

# Unix/macOS
CONFIGCAT_API_USER=your_user CONFIGCAT_API_PASS=your_pass npx -y @configcat/mcp-server

# Windows (PowerShell)
$env:CONFIGCAT_API_USER="your_user"; $env:CONFIGCAT_API_PASS="your_pass"; npx -y @configcat/mcp-server

Editor integration examples

• Cursor (custom MCP):

{
  "mcpServers": {
    "ConfigCat": {
      "command": "npx",
      "args": ["-y", "@configcat/mcp-server"],
      "env": {
        "CONFIGCAT_API_USER": "YOUR_API_USER",
        "CONFIGCAT_API_PASS": "YOUR_API_PASSWORD"
      }
    }
  }
}

• Visual Studio Code (.vscode/mcp.json):

{
  "servers": {
    "ConfigCat": {
      "command": "npx",
      "args": ["-y", "@configcat/mcp-server"],
      "env": {
        "CONFIGCAT_API_USER": "YOUR_API_USER",
        "CONFIGCAT_API_PASS": "YOUR_API_PASSWORD"
      }
    }
  }
}

• Claude Desktop (claude_desktop_config.json snippet):

{
  "mcpServers": {
    "ConfigCat": {
      "command": "npx",
      "args": ["-y", "@configcat/mcp-server"],
      "env": {
        "CONFIGCAT_API_USER": "YOUR_API_USER",
        "CONFIGCAT_API_PASS": "YOUR_API_PASSWORD"
      }
    }
  }
}

After configuring, restart the editor or the desktop app if required. The editor can then query the MCP server for flag lists, SDK snippets and management operations.

Available Tools / Resources

The MCP server exposes a broad set of tools that map to ConfigCat Management API operations. Major categories include:

• Membership Management
  • Organizations: list organizations
  • Members: list members, invite member, update permissions, delete member
  • Permission Groups: CRUD permission groups
• General Management
  • Products: list/create/update/delete products and preferences
  • Configs: list/create/get/update/delete configs
  • Environments: list/create/get/update/delete environments
  • Segments: list/create/get/update/delete segments
  • SDK Keys: retrieve SDK keys for a config/environment
• Integrations & Webhooks
  • List/create/get/update/delete integrations and webhooks
  • Manage webhook signing keys
• Diagnostics
  • Audit logs: list product audit logs
• Code References
  • get-code-references: fetch references to feature flags in code (used by editor features)

Each tool is exposed as a discrete command endpoint that editors or integrations can call to perform operations or to retrieve documentation and SDK snippets.

Use Cases

• Editor-aware completions and validation
  • An editor extension queries the MCP server to list the current feature flags for a product and provides auto-complete when developers reference flags in code. This reduces typos and enforces consistent flag names.
• Create flags in-code
  • A developer can trigger an “add feature flag” flow from inside their editor. The MCP server creates the flag in ConfigCat and the editor inserts the flag id into the code automatically.
• Generate SDK integration snippets
  • When adding a new feature, the editor can fetch language-specific SDK examples from the MCP server so developers get copy-paste-ready integration code for JavaScript, .NET, Java, etc.
• CI / automation scripts
  • Use the MCP server tooling in automation scripts to create temporary feature flags for testing environments, rotate SDK keys, or adjust environment configs as part of a pipeline.
• Audit and compliance
  • Retrieve audit logs via the MCP server to show change history for feature flags and user membership actions, useful for reviews and compliance audits.

Getting help

• Source code and issues: https://github.com/configcat/mcp-server
• Refer to ConfigCat Management API docs for API-level details and rate limits: https://configcat.com/docs/api/reference/configcat-public-management-api/

Run the server locally with your management API credentials and connect your editor to experience in-editor feature flag management and streamlined SDK onboarding.