ConfigDirector MCP Service

Manage ConfigDirector feature flags, remote configs, and targeting rules from AI assistants.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

  • List Projects: List the projects in the organization with their ids and slugs. Environments are not included; call list_environments for a project.
  • Get Project: Get one project by id, including its environments when the token can read environments.
  • Create Project: Create a project in the organization. The Test and Production environments are created with it. The slug is the URL-safe identifier: lowercase letters and digits, with single hyphens o

What data it sees

Do you need an account

An API key from the service settings is required

Manage ConfigDirector feature flags, remote configs, and targeting rules from AI assistants.

How to connect

How to connect ConfigDirector MCP Service to Claude

The server address to paste into Claude settings:

https://admin-mcp--configdirector.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect ConfigDirector MCP Service to ChatGPT

The server address to paste into ChatGPT settings:

https://admin-mcp--configdirector.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect ConfigDirector MCP Service to Cursor

The server address to paste into Cursor settings:

https://admin-mcp--configdirector.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (15)

Raw names from tools/list. Only developers need these.

list_projectsList the projects in the organization with their ids and slugs. Environments are not included; call list_environments for a project.
get_projectGet one project by id, including its environments when the token can read environments.
create_projectCreate a project in the organization. The Test and Production environments are created with it. The slug is the URL-safe identifier: lowercase letters and digits, with single hyphens or underscores between them, unique in the organization, not a UUID.
update_projectRename a project or change its slug. Both fields are required; send the current value for the one you keep. The slug is the URL-safe identifier: lowercase letters and digits, with single hyphens or underscores between them, unique in the organization, not a UUID.
list_environmentsList the environments of a project with their ids, slugs, and whether each one is live (serving real users).
get_environmentGet one environment of a project by id.
create_environmentCreate an environment in a project. The slug is the URL-safe identifier used by SDKs and Terraform (lowercase letters, digits, and hyphens, at least 4 characters, unique in the project). The color is for the dashboard. Set live to true for environments that serve real users; the dashboard asks for confirmation before changing targeting rules in a live environment.
update_environmentUpdate an environment's name, slug, color, or live flag. All four fields are required; send the current values for the ones you keep. The slug is the URL-safe identifier used by SDKs and Terraform (lowercase letters, digits, and hyphens, at least 4 characters, unique in the project). The color is for the dashboard. Set live to true for environments that serve real users; the dashboard asks for confirmation before changing targeting rules in a live environment.
list_configsList the configs of a project: key, role (feature flag, kill switch, config, experiment), lifetime, type, and constraints. Targeting rules are not included; call get_config for one config's rules.
get_configGet one config by key, including its targeting rules for every environment (the targets array, one entry per environment with the ordered rules and the default targeting rule value, defaultValue, returned when no rule matches). Each target names its environment as an object, environment: { id, name, slug, color, live }; pass targets[].environment.id as the environmentId of update_targeting_rules and targets[].defaultValue as its defaultValue.
get_config_activityGet the most recent evaluation of a config reported by SDK telemetry, per environment, SDK key kind, SDK name, and SDK version, most recent first. Useful to tell whether a config is still in use.
create_configCreate a config (feature flag, kill switch, config value, or experiment) in a project. defaultValue is the initial default targeting rule value: the catch-all rule of every environment starts with it. It is not the in-code default value the application passes to the SDK. See each parameter for its format; call list_configs to see how existing configs are set up.
update_config_settingsChange the settings of a config: lifetime, description, role, type, typeOptions, variations, availability ({ server, client }), or key (renaming keeps the old key working for SDKs). Send only the fields to change. Targeting rules are changed with update_targeting_rules. Changing a JSON Schema re-validates every value in every environment and is rejected if one no longer matches. See each parameter for its format; call list_configs to see how existing configs are set up.
update_targeting_rulesReplace the targeting rules of one config in one environment. The call replaces every rule for that environment: send the complete rules array in evaluation order, reusing the ids of the rules, conditions, and percentages you keep from get_config and new UUIDs for new ones. environmentId is targets[].environment.id in get_config (there is no environmentId field there), or the id from list_environments. defaultValue is the default targeting rule value, returned when no rule matches (the catch-all rule); it is not the in-code default value the application passes to the SDK. Values are sent as strings in the config's type. Text and array conditions match case-sensitively. Every value is checked against the config's type and JSON Schema before anything changes. Call get_targeting_rules_reference for the exact rule format.
get_targeting_rules_referenceThe exact format update_targeting_rules accepts: the JSON Schema of a targeting rules update, the operators allowed per target type, the attributes a condition can test, and notes on how rules are evaluated. Read this before composing rules.