Skip to main content
Glama
featureflow

Featureflow MCP Server

Official
by featureflow

Related Servers

Alternatives to Featureflow MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      49,401 npm
      28
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.
      6,446 npm
      20
      MIT
    • A
      license
      A
      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.
      19
      350 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to manage Unleash feature flags, including creation, detection, evaluation, and best practices.
      11
      600 npm
      22
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with PostHog's product analytics platform through natural language, allowing users to manage feature flags, view errors, and access other platform features.
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity, as they target specific resources (feature, environment, project, target, API key) and actions (create, get, list, update, delete, clone, archive). Overlap is minimal, such as 'get_feature' and 'get_feature_control' which serve different levels of detail, and descriptions clarify boundaries effectively.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly (e.g., create_feature, list_environments, update_project). The naming convention is predictable, making it easy for agents to infer functionality and maintain readability across all 22 tools.

    Tool Count4/5

    With 22 tools, the count is slightly high but reasonable for a feature flag management system, covering CRUD operations for multiple resources (features, environments, projects, targets, API keys). It feels comprehensive rather than bloated, though it borders on the upper limit of typical scoping (3-15 tools).

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for the feature flag management domain, including creation, retrieval, listing, updating, deletion, and specialized operations like cloning and archiving. No obvious gaps exist; agents can perform all core workflows without dead ends, from project setup to feature control updates.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues