Skip to main content
Glama
kud

@kud/mcp-harness-fme

by kud

Related Servers

Alternatives to @kud/mcp-harness-fme

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Manage 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 npm
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      22
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      27
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Provides 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.
      95
      677 npm
      17
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides access to the ABsmartly experimentation platform with 230+ commands across 33 groups for experiment lifecycle, metrics, goals, teams, etc.
      -

    TDQS

    A3.6/5.0

    Scored across 30 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessResponsive