Bucketeer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (error, warn, info, debug) | info |
| BUCKETEER_HOST | No | Bucketeer API host URL | api.bucketeer.io |
| BUCKETEER_API_KEY | Yes | Your Bucketeer API key with appropriate permissions (READ, WRITE, or ADMIN) | |
| BUCKETEER_ENVIRONMENT_ID | Yes | Your Bucketeer environment ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listFeatureFlagsC | List all feature flags in the specified environment |
| createFeatureFlagC | Create a new feature flag in the specified environment |
| getFeatureFlagC | Get a specific feature flag by ID |
| updateFeatureFlagC | Update an existing feature flag |
| archiveFeatureFlagC | Archive a feature flag (make it inactive) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting specific CRUD operations on feature flags: list (retrieve all), get (retrieve one), create (add new), update (modify existing), and archive (deactivate). No ambiguity exists between these actions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (e.g., listFeatureFlags, createFeatureFlag) with perfect adherence to camelCase. The naming is predictable and readable across all five tools, with no deviations in style or convention.
With 5 tools, this server is well-scoped for managing feature flags, covering essential CRUD operations plus archiving. Each tool earns its place without redundancy, and the count is appropriate for the domain, avoiding being too sparse or bloated.
The tool set provides complete lifecycle coverage for feature flags: create, read (list and get), update, and archive (as a soft delete). There are no obvious gaps, and agents can perform all core operations without dead ends in the domain of feature flag management.