ConfigCat MCP Server
OfficialRelated Servers
Alternatives to ConfigCat MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAllows programmatic management of a Dify instance, including listing and creating datasets, managing applications, and tool providers.-
- FlicenseNot gradedqualityFmaintenanceEnables interaction with the Productboard REST API, providing tools to manage features, notes, companies, objectives, initiatives, key results, releases, webhooks, users, products, and components.-
- AlicenseCqualityDmaintenanceInteract with Descope's Management APIs to manage users, audit, and more.438MIT
- AlicenseNot gradedqualityBmaintenanceEnables inspecting projects, environments, feature rollouts, and experiment-linked flags through LaunchDarkly's REST API.373 npmMIT

OpenCDR MCPofficial
AlicenseAqualityBmaintenanceEnables MCP-compatible clients to access a deployed management API through tools for status, detection and correlation rules, lists, signals, logs, integrations, notification settings, and incident-response roles/actions, with capability profiles and API-key scope enforcement.14Mozilla Public 2.0- FlicenseNot gradedqualityDmaintenanceEnables programmatic management of a Dify instance, including datasets, apps, and tools.-
TDQS
Scored across 96 tools
The tool set contains many overlapping operations, especially around setting values: get-setting-value, get-setting-value-v2, get-setting-values, get-setting-values-v2, replace-setting-value, update-setting-value, post-setting-values, and their v2 variants are hard to distinguish without deep API knowledge. Plural/singular, batch vs single, and v1/v2 distinctions create real misselection risk.
Most tools follow a predictable kebab-case verb_noun pattern (list-products, get-config, create-webhook, delete-segment). There are minor deviations such as get-sdk-documentation, list-pending-invitations-org, and the v2 suffixes, but the overall convention is consistent and readable.
96 tools is far beyond a reasonable set for agent use, even for a large management API. The surface includes many fine-grained and redundant v1/v2 operations, making the tool list unwieldy and increasing selection burden.
The server covers a broad lifecycle across organizations, products, configs, environments, feature flags, setting values, tags, segments, webhooks, integrations, permission groups, members, invitations, audit logs, and change requests. A few possible gaps remain, such as organization creation, but core workflows are well covered.