4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
ConfigCat MCP Server

Bring Feature Flags
to CrewAI

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

MCP Inspector 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

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
ConfigCat

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

  1. Subscribe to this server
  2. Enter your ConfigCat API Key ID and Secret
  3. 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 CrewAI?

When paired with CrewAI, ConfigCat becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ConfigCat tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

ConfigCat in CrewAI

AI AgentVinkius
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 CrewAI 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 catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for ConfigCat in CrewAI

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 CrewAI 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.

ConfigCat
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 CrewAI

Every tool call from CrewAI 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

01

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.

02

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.

03

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.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →