Mcp
Manage ConfigDirector feature flags, remote configs, and targeting rules from AI assistants.
- Transport
- Not stated
- Package
- —
- Registry id
- com.configdirector/mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
The ConfigDirector MCP server allows AI coding assistants to read and update projects, environments, configs, and targeting rules. The server runs as a hosted endpoint requiring no installation. The server communicates via the Model Context Protocol over Streamable HTTP and authenticates with a ConfigDirector API token.
Tool calls are billed as Admin API requests, with one tool call equaling one Admin API request. The server only exposes tools matching the token's permissions, making a read-only token result in a read-only assistant. An organization is limited to 60 tool calls per minute across all tokens.
Every update is logged in the config's audit log with the source "MCP" and the token owner's name. The MCP server does not return SDK keys or API tokens.
Summary drafted from the project's own website. Every sentence is backed by text on that page and was reviewed before publishing.