F
licenseNot graded
qualityC
maintenanceAllows programmatic management of a Dify instance, including listing and creating datasets, managing applications, and tool providers.
-
ConfigCat MCP Server
Officialby configcat
Related Servers
Alternatives to ConfigCat MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseCqualityFmaintenanceInteract with Descope's Management APIs to manage users, audit, and more.436MIT
- AlicenseNot gradedqualityCmaintenanceEnables inspecting projects, environments, feature rollouts, and experiment-linked flags through LaunchDarkly's REST API.MIT
- FlicenseNot gradedqualityDmaintenanceEnables programmatic management of a Dify instance, including datasets, apps, and tools.-
- AlicenseNot gradedqualityCmaintenanceEnables interaction with LaunchDarkly's feature flag platform through AI clients. Supports managing feature flags, AI configs, and their variations with operations like create, update, delete, and targeting configuration.49,401 npm28MIT
TDQS
C2.7/5.0
Scored across 95 tools
Disambiguation2/5
The v1/v2 tool pairs (get-setting-value/get-setting-value-v2, replace-setting-value/replace-setting-value-v2, update-setting-value/update-setting-value-v2, etc.) perform essentially the same operations with different response schemas, and no deprecation guidance helps agents choose. Additionally, update-setting vs update-setting-value vs replace-setting-value have subtle boundaries that names alone don't clarify.
Naming Consistency3/5
The dominant pattern is consistent snake_case verb_noun (list-configs, create-environment, update-segment, delete-tag). However, there are notable deviations: list-staleflags lacks a separator, post-setting-values uses 'post' where every other full-replace endpoint uses 'replace', v2 suffixes appear inconsistently, and update-sdk-documentation breaks the resource-based convention entirely.
Tool Count1/5
95 tools is an extreme count, well beyond even the 50+ threshold for a 1. While the ConfigCat Management API is genuinely broad, exposing nearly the entire API surface as individual MCP tools creates an overwhelming selection space for agents, especially with the redundant v1/v2 duplicates inflating the count.
Completeness4/5
The surface covers full CRUD for products, configs, environments, settings, segments, tags, webhooks, integrations, and permission groups, plus a rich change-request lifecycle. Minor gaps exist (no get/update/delete for organizations, no listing of change-request comments, no update/resend for invitations), but core workflows have no dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues