Compatible with every major AI agent and IDE
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 a new configuration
Create a new environment
Create a new segment
Create a new feature flag or setting
Delete a configuration
Delete an environment
Delete a segment
Delete a setting
Get details of a specific configuration
Get details of an environment
Get details of a segment
Get details of a setting
Get the value of a setting in an environment
List all configurations in a product
g., Test, Production) for a specific product. List all environments in a product
List all segments in a product
List all settings in a configuration
Update the value/targeting of a setting
Why Claude Desktop?
Claude Desktop is the definitive way to connect ConfigCat to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 18 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
ConfigCat in Claude Desktop
ConfigCat and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ConfigCat to Claude Desktop 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 ConfigCat in Claude Desktop
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 Claude Desktop 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
ConfigCat for Claude Desktop
Every tool call from Claude Desktop to the ConfigCat MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Joomag
10 toolsManage digital publications, issues, and analytics via Joomag API.

Microsoft Clarity
13 toolsSee exactly how users interact with your website through heatmaps, session recordings, and behavioral analytics that reveal UX insights.

Portable.io
6 toolsManage your Portable ETL pipelines directly via your AI agent — monitor flows, sync runs, and destination details seamlessly.

Basecamp
7 toolsManage your Basecamp projects via AI — list tasks, read message boards, track campfire logs, and orchestrate to-dos seamlessly.
