@kud/mcp-harness-fme
Related Servers
Alternatives to @kud/mcp-harness-fme
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceManage Featureflip feature flags, targeting and rollouts from AI agents and editors. 19 tools over the public Management API let agents read flag state, create and toggle flags, edit targeting rules, manage segments and find stale flags from Claude Code, Cursor, Cline or any MCP-compatible client. Every tool is annotated read-only or destructive. Apache-2.0.47 npmApache 2.0- AlicenseAqualityDmaintenanceEnables AI assistants to manage Featureflow feature flags, including creating and updating features, controlling feature states across environments, and managing projects, environments, and targeting rules through natural language.225 npmMIT
- 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.56,893 npm27MIT

ConfigCat MCP Serverofficial
AlicenseCqualityAmaintenanceProvides access to ConfigCat's management API for feature flag and configuration management, enabling CRUD operations on entities like feature flags, configs, environments, and products, as well as SDK documentation.95677 npm17MIT
ABsmartly MCP Serverofficial
FlicenseNot gradedqualityCmaintenanceProvides access to the ABsmartly experimentation platform with 230+ commands across 33 groups for experiment lifecycle, metrics, goals, teams, etc.-- FlicenseNot gradedqualityDmaintenanceEnables AI applications to manage continuous delivery and cloud costs through the Harness platform.2-
TDQS
Scored across 30 tools
Most tools have distinct purposes, but potential overlap exists between add_segment_to_treatment and update_flag_definition, and among the various segment list tools (list_segments, list_rule_based_segments, list_rule_based_segment_definitions). Descriptions help clarify, but an agent might still misselect.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_feature_flag, list_environments, update_flag_definition. No mixing of conventions.
With 30 tools, the set is slightly over the typical well-scoped range (3-15), but it covers a complex domain (feature flag management with many sub-resources). Each tool seems justified, though some granularity could be reduced.
The tool set provides comprehensive CRUD and lifecycle operations for feature flags, segments, environments, workspaces, and more. Includes advanced operations like rollback, change requests, and deep-links. No obvious gaps for the intended domain.