What is a #feature-flags MCP server?
An MCP server tagged #feature-flags implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access feature-flags-related tools, data, or APIs.
Every MCP server and client below is tagged #feature-flags — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to feature-flags tools.
growthbook
Official GrowthBook MCP server for creating flags, getting experiments, and more.
configcat
Enables AI tools to interact with ConfigCat, a feature flag service for teams. Supports managing ConfigCat feature flags, configs, environments, products and organizations. Helps to integrate ConfigCat SDK, implement feature flags and remove zombie (stale) flags.
bucketco
Flag features directly from chat in your code editor, including VS Code, Cursor, Windsurf, Claude Code—any IDE with MCP support.
statsig-io
Bridges directly to Statsig, enabling you to wrap new features behind feature flags, add instrumentation for product performance visibility, and seamlessly highlight and clean up stale feature flags from your codebase.
Flagsmith
Create, manage, and clean up Flagsmith feature flags directly from your AI tool. Flagsmith is an open source feature flag and remote config platform you can self-host or run in the cloud, and the MCP server lets you control flags, environments, and segments through natural langua
Common questions about MCP servers and clients tagged #feature-flags
An MCP server tagged #feature-flags implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access feature-flags-related tools, data, or APIs.
mcp.so currently lists 5 MCP servers and clients tagged #feature-flags.
Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.