Skip to main content
Glama
canopy-labs

Featureflip

Official

Related Servers

Alternatives to Featureflip

No user-submitted related servers found.

    Related Servers

    • 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
      10 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.
      30,145 npm
      27
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.
      11,185 npm
      20
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI assistants manage a StreamElements channel by wrapping the full REST API as tools, covering the chat bot, commands, timers, filters, loyalty points, store, tips, song requests, contests, giveaways and overlays. Supports toolsets, read-only mode and safety annotations so clients can restrict or gate risky operations.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to manage a self-hosted Coolify instance, including applications, databases, services, servers, projects, deployments, environment variables, tags, teams, private keys, and S3 backup storages via the Coolify REST API.
      359 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 26 tools

    Disambiguation3/5

    Most tools target distinct resources or actions, but find_stale_flags and list_removal_candidates both surface flags for cleanup with overlapping descriptions, and create_flag and wrap_feature both create flags. Descriptions help differentiate, yet an agent could still misselect between these pairs.

    Naming Consistency4/5

    Tool names are consistently snake_case and nearly all follow a verb_noun pattern (list_flags, get_flag, update_targeting, etc.). The only minor deviation is flag_status, which is noun-first, but it remains readable and consistent in style.

    Tool Count2/5

    With 26 tools, the server is on the heavy side for its purpose. Several operations could be consolidated (e.g., flag_status into get_flag, find_stale_flags and list_removal_candidates into one parameterized tool), making the surface larger than necessary despite a broad domain.

    Completeness4/5

    The set covers core feature flag lifecycle (create, read, update, delete, archive, restore), targeting, variations, cleanup, and webhooks well. Minor gaps exist for segments and environments (only list/get, no create/update/delete), but these are likely managed elsewhere and don't block core workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues