Connect ConfigCat to Claude Code
Read and change feature flags, their per-environment values, configs and the audit log in ConfigCat. Add Toolspoke to Claude Code once and it can use 15 ConfigCat actions. Your ConfigCat credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install ConfigCat and connect it
Add ConfigCat to a project in your Toolspoke workspace.
Management API credentials. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- Basic auth username and password
- ConfigCat → your avatar → Public API credentials (https://app.configcat.com/my-account/public-api-credentials) → Add new credentials. Paste the Basic auth username, a colon, then the password. The credentials act with your own permissions in every organization you belong to, so a member of a read-only permission group gets read-only access here.
Choose what Claude Code may do
All 15 actions start on. Switch off any of the 3 actions that change something in ConfigCat, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the ConfigCat actions that only read, so they are safe to try first.
- List the organizations these credentials belong to
- List every product these credentials can see, across all organizations
- List the configs in one product
- List the environments in one product, such as Test and Production
What Claude Code can do in ConfigCat
12 actions read, 2 write and one deletes or permanently changes something.
Reads
List organizations
List the organizations these credentials belong to. The organization id is what audit and member reads at organization level take.
List products
List every product these credentials can see, across all organizations. Start here, the product id is what configs, environments, tags, segments and audit logs are listed under, and it is the install's connection test, because it fails when the credentials reach nothing.
List configs
List the configs in one product. A config holds a set of feature flags and settings; its id is what list_settings and get_config_values take.
List environments
List the environments in one product, such as Test and Production. Every value read or change names one environment.
List settings
List the feature flags and settings defined in one config, with each one's numeric id, key, type and tags. Values are per environment and are read separately.
Get setting
Read one feature flag or setting's definition, key, name, hint, type and tags, by its numeric id.
Get setting value
Read what one flag or setting serves in one environment, its defaultValue, its ordered targetingRules and the percentage evaluation attribute. The rules are evaluated in the order returned.
Get config values
Read the values of every flag and setting in one config for one environment, in a single call. Cheaper than calling get_setting_value once per flag.
List tags
List the tags defined in one product. A tag id is what create_setting takes to label a flag.
List segments
List the user segments defined in one product. Segments are reusable targeting conditions that targeting rules refer to by id.
List stale flags
List flags in one product that have not changed for a while, the candidates for removing from code and then deleting.
List audit logs
List the audit log for one product, who changed which flag, config or environment, and when, optionally narrowed to one config, one environment or a time window.
Writes
Update setting value
Change what one flag or setting serves in one environment, with a list of JSON Patch operations. Only defaultValue, targetingRules and percentageEvaluationAttribute can be changed. To switch a boolean flag on, send [{"op": "replace", "path": "/defaultValue/boolValue", "value": true}]; string, int and double settings use stringValue, intValue and doubleValue. This takes effect for every SDK reading the environment, so read the current value first with get_setting_value. A write, not destructive: the previous value can be set back, and the audit log records the change.
Create setting
Create a feature flag or setting in one config. It starts with the type's empty value in every environment and serves nothing new until a value is set, so creating one changes no running app.
Deletes or permanently changes
Delete setting
Delete a feature flag or setting, with its values in every environment. Destructive because there is no undo, and any SDK still reading the key falls back to its own default from then on.
ConfigCat in Claude Code: questions
Does Claude Code see my ConfigCat credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in ConfigCat?
Yes. Each of the 15 actions can be switched off for a project. Turn off the 3 that change something and Claude Code can only read.
Will 15 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the ConfigCat action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a ConfigCat call does not run in a sandbox, so it bills nothing.
ConfigCat in your other apps
Try ConfigCat in Claude Code
Free to start, and tool calls cost nothing on any plan.