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 Cursor?
Cursor's Agent mode turns ConfigCat into an in-editor superpower. Ask Cursor to generate code using live data from ConfigCat and it fetches, processes, and writes. all in a single agentic loop. 18 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
ConfigCat in Cursor
ConfigCat and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ConfigCat to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Aero Workflow
12 toolsOrganize accounting firm tasks, track client work, and manage team workloads with purpose-built practice management.

360dialog
10 toolsSend WhatsApp messages at scale, manage templates, and track delivery with the official 360dialog Business API integration.

Geekflare
7 toolsTest your website performance, security headers, and DNS configuration with a comprehensive suite of technical audit tools.

Lanhu
10 toolsProduct design collaboration platform — manage design files, handoffs, and team feedback via AI.
