Skip to main content
Glama
Sign In
Bucketeer MCP Server

Bucketeer MCP Server

Official
by bucketeer-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bucketeer MCP Server

No user-submitted related servers found.

    Related Servers

    • Bucketeer MCP Server

      nnnkkk7
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for managing Bucketeer feature flags, providing tools for listing, creating, retrieving, updating, and archiving feature flags.
      5
      1
      MIT
    • hackle-mcp

      hackle-mcpofficial

      hackle-io
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server for Hackle API providing tools and resources for querying A/B Test data.
      19
      40 npm
      3
      MIT
    • Flagsmith

      Flagsmithofficial

      Flagsmith
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Flagsmith's Core and SDK APIs, enabling management of feature flags and configurations.
      177,494 npm
      BSD 3-Clause

    • Unleash Feature Flag MCP

      ylin6
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that allows AI assistants to programmatically manage Unleash feature flags through natural language, enabling operations like creating, updating, and retrieving feature flags across projects.
      5
      7 npm
      3
      ISC
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: archive, create, get, list, and update are all unique actions targeting feature flags. The descriptions reinforce this by specifying distinct operations (e.g., 'make it inactive' vs. 'create a new feature flag'), making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., archiveFeatureFlag, createFeatureFlag) with identical casing (camelCase) and the same noun ('FeatureFlag') throughout. This predictable pattern enhances readability and agent usability.

    Tool Count5/5

    With 5 tools, the count is well-scoped for managing feature flags, covering core CRUD operations (create, get, update, list) plus archiving. Each tool earns its place without bloat, aligning with typical server scopes of 3-15 tools for focused domains.

    Completeness5/5

    The tool set provides complete lifecycle coverage for feature flags: creation, retrieval (get and list), updating, and archiving (deactivation). No obvious gaps exist, as agents can perform all essential operations without dead ends in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources