Most feature flag work happens in two places at once. You write the code that reads the flag in your editor, then switch to a dashboard to create the flag, enable it for dev/test, and later roll it out in production. With the ConfigDirector MCP server, the code assistant that is already in your editor can do the second half for you.
What the MCP server is
The Model Context Protocol is how coding assistants such as Claude Code, Cursor, and Copilot interact with outside tools. A server exposes a set of tools, the assistant reads the tool descriptions and calls them when a task needs them.
ConfigDirector's MCP server is hosted, so there is nothing to install or run. It sits in front of the same Admin API that the dashboard and the Terraform provider use, and it authenticates with an ordinary API token. Every update it makes goes through the same validation as an update from the dashboard, it is recorded in the audit log with the source MCP, and counts as one Admin API request per tool call.
Connecting Claude Code
Create an API token in the dashboard with the permissions you want the assistant to have. For a first try, read permissions on projects, environments, and configs are enough to explore. To support a full workflow, add the create, update settings, and update targeting rules permissions on configs. Copy the token to your clipboard before dismissing the page (the token is only shown at creation time).
Then add the MCP server to claude. The token is read from an environment variable, so it never lands in a file you might commit:
claude mcp add --transport http configdirector https://mcp.configdirector.com \
--header "Authorization: Bearer ${CONFIGDIRECTOR_TOKEN}"
Type /mcp inside Claude Code and the server shows as connected, with only the tools your token allows. Cursor, VS Code, Windsurf, Codex CLI, and Gemini CLI each have a two-line setup of their own. The MCP docs page has all of them.
A session
Here is what an ordinary afternoon looks like once the server is connected. Each request is typed to the assistant in plain words, the tool calls happen underneath.
Creating a kill switch. "Create a kill switch called payments-v2 in the checkout project, off in every environment." The assistant lists the projects to find checkout, creates the config with the kill switch role, and reports the key. The switch is off in every environment because that is the initial default targeting rule value it was created with.
Rolling out a flag. "In production, roll new-search out to 10 percent of users, and to everyone whose email ends in @example.com." The assistant reads the flag's current rules for production, then replaces them with two rules: a conditional rule that matches the email domain, and a percentage rule that splits the rest. Because the MCP server provides the assistant with the exact targeting rules format and the operators each attribute supports, it does not have to guess.
Checking what is still in use. "Which flags in the checkout project have not been evaluated in the last week?" The assistant reads the recent evaluation activity of each config, which comes from the SDKs' telemetry, and tells you which ones have not been requested by any SDK. Those are the candidates for cleanup, and the dashboard is where you archive them.
Open the audit log afterwards and each change is there, attributed to the token's owner with the source MCP, next to the changes made from the dashboard and from Terraform.
What the server will not do
The assistant only sees the tools its token has permission for. A read-only token produces a read-only assistant. There is no tool to archive a config, or to delete a project or an environment. Those destructive operations stay in the dashboard on purpose.
Each organization can make up to 60 tool calls per minute. Past that, the assistant is told to wait for the next minute rather than being cut off, which keeps a retry loop from doing any harm.
Try it
The docs page has the setup for every supported tool and the full list of what the assistant can do. If you already use ConfigDirector, an API token is all you need. If you do not, the Free plan includes the MCP server.
