ConfigCat Targeting and Access (BYOK) — connector documentation
- MCP endpoint:
https://byok-configcat-targeting.connectorbay.com/mcp - REST API:
POST https://byok-configcat-targeting.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-configcat-targeting.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own ConfigCat Targeting and Access Public API basic auth username, sent in the
X-Upstream-Keyheader and the Public API basic auth password inX-Upstream-Key-2of every request (never stored, logged or cached) - Health:
https://byok-configcat-targeting.connectorbay.com/health· Tool schemas:https://byok-configcat-targeting.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-configcat-targeting · agent@connectorbay.com
What ConfigCat Targeting and Access (BYOK) is for
ConfigCat Targeting and Access (BYOK) lets an AI assistant read your own ConfigCat Targeting and Access data through the ConfigCat Targeting and Access API with a key you supply (Public API basic auth username). Read-only: 9 tools (get_flag, get_environment_flag_values, list_flags_by_tag, list_deleted_flags, get_segment, list_permission_groups, get_permission_group, get_config, get_environment). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.configcat.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ConfigCat Targeting and Access. ConfigCat Targeting and Access and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Show ConfigCat flag 1234"
- "What are all the flag values and targeting rules of the Production environment in ConfigCat?"
- "Which ConfigCat flags are tagged checkout?"
- "Which flags were deleted from my ConfigCat config?"
- "What is the ConfigCat segment beta-testers?"
- "Which permission groups does my ConfigCat product have?"
What it does
get_flag: Get one feature flag or setting (by id) with key, name, hint, value type, config and tags.get_environment_flag_values: Get the current value of every flag of a config in one environment, with the percentage rollout items and targeting rules (comparison attribute, comparator, compared value; the values can contain customer identifiers you chose to target) and last update time.list_flags_by_tag: List the flags that carry a given tag, with key, name, type, hint and config.list_deleted_flags: List the flags that were deleted from a config, with key, name, type and hint.get_segment: Get one segment (reusable targeting group) with its name, description, comparison attribute and comparator, creation and update dates. The compared values are not returned.list_permission_groups: List the permission groups of a product with access type, key capability flags and per-environment access. Members are not listed.get_permission_group: Get one permission group with its access type, capability flags and per-environment access.get_config: Get one config (flag container) with its name, description, evaluation version and order.get_environment: Get one environment with its name, description, color and whether changes need a reason or approval.
BYOK key
You bring your own ConfigCat Targeting and Access Public API basic auth username (https://app.configcat.com/my-account/public-api-credentials). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.configcat.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://api.configcat.com/docs/ (the API this connector calls, with a BYOK key)
Live from the ConfigCat Targeting and Access API (api.configcat.com) with a BYOK key; documentation: https://api.configcat.com/docs/. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ConfigCat Targeting and Access. ConfigCat Targeting and Access and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your ConfigCat Targeting and Access account.
Built for: Worldwide. Languages: English.