Bucketeer MCP Server
Uses environment variables for configuration through a .env file, allowing users to securely store and access their Bucketeer credentials and settings.
Runs on Node.js platform (version 18 or higher), leveraging it to implement the MCP server for Bucketeer feature flag management.
Built with TypeScript for type safety and better developer experience, as evidenced by the project structure including TypeScript configuration and type definitions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bucketeer MCP Server list all active feature flags for the checkout flow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bucketeer MCP Server
A Model Context Protocol (MCP) server for managing feature flags in Bucketeer, an open-source feature flag management platform.
Features
This MCP server provides tools for basic CRUD operations on Bucketeer feature flags:
listFeatureFlags - List all feature flags with filtering and pagination
createFeatureFlag - Create a new feature flag
getFeatureFlag - Get a specific feature flag by ID
updateFeatureFlag - Update an existing feature flag
archiveFeatureFlag - Archive a feature flag (make it inactive)
Related MCP server: hackle-mcp
Prerequisites
Node.js 18 or higher
A Bucketeer instance with API access
An API key with appropriate permissions (READ, WRITE, or ADMIN)
Installation
Clone this repository:
git clone https://github.com/yourusername/bucketeer-mcp.git
cd bucketeer-mcpInstall dependencies:
npm installBuild the project:
npm run buildCreate a
.envfile based on.env.example:
cp .env.example .envConfigure your environment variables in
.env:
BUCKETEER_HOST=api.bucketeer.io
BUCKETEER_API_KEY=your-api-key-here
BUCKETEER_ENVIRONMENT_ID=your-environment-id
LOG_LEVEL=infoUsage
Running the Server
Start the MCP server:
npm startFor development with auto-reload:
npm run devMCP Client Configuration
To use this server with an MCP client, add it to your MCP client configuration:
{
"mcpServers": {
"bucketeer": {
"command": "node",
"args": ["/path/to/bucketeer-mcp/dist/index.js"],
"env": {
"BUCKETEER_HOST": "api.bucketeer.io",
"BUCKETEER_API_KEY": "your-api-key",
"BUCKETEER_ENVIRONMENT_ID": "your-environment-id"
}
}
}
}Available Tools
listFeatureFlags
List all feature flags in the specified environment.
Parameters:
environmentId(optional) - Environment ID (uses default if not provided)pageSize(optional) - Number of items per page (1-100, default: 20)cursor(optional) - Pagination cursor for next pagetags(optional) - Filter by tagsorderBy(optional) - Field to order by (CREATED_AT, UPDATED_AT, NAME)orderDirection(optional) - Order direction (ASC, DESC)searchKeyword(optional) - Search keyword for feature name or IDmaintainer(optional) - Filter by maintainer emailarchived(optional) - Filter by archived status
createFeatureFlag
Create a new feature flag.
Parameters:
id(required) - Unique identifier (alphanumeric, hyphens, underscores)name(required) - Human-readable namedescription(optional) - Description of the feature flagenvironmentId(optional) - Environment ID (uses default if not provided)variations(required) - Array of variations (at least 2)value(required) - The value returned when this variation is servedname(required) - Name of the variationdescription(optional) - Description of the variation
tags(optional) - Tags for the feature flagdefaultOnVariationIndex(required) - Index of variation when flag is on (0-based)defaultOffVariationIndex(required) - Index of variation when flag is off (0-based)variationType(optional) - Type of the variation values: STRING (default), BOOLEAN, NUMBER, or JSON
getFeatureFlag
Get a specific feature flag by ID.
Parameters:
id(required) - The ID of the feature flag to retrieveenvironmentId(optional) - Environment ID (uses default if not provided)featureVersion(optional) - Specific version of the feature to retrieve
updateFeatureFlag
Update an existing feature flag.
Parameters:
id(required) - The ID of the feature flag to updatecomment(required) - Comment for the update (required for audit trail)environmentId(optional) - Environment ID (uses default if not provided)name(optional) - New name for the feature flagdescription(optional) - New descriptiontags(optional) - New tagsenabled(optional) - Enable or disable the feature flagarchived(optional) - Archive or unarchive the feature flag
Note:
This tool requires a comment for audit trail purposes
It does not support updating variations. To modify variations, you would need to archive the current flag and create a new one.
archiveFeatureFlag
Archive a feature flag (make it inactive). Archived flags will return the default value defined in your code for all users.
Parameters:
id(required) - The ID of the feature flag to archiveenvironmentId(optional) - Environment ID (uses default if not provided)comment(required) - Comment for the archive action (required for audit trail)
Note: This operation archives the flag rather than permanently deleting it. The flag can be unarchived later if needed.
API Key Permissions
Different operations require different permission levels:
READ: Required for listFeatureFlags and getFeatureFlag
WRITE: Required for createFeatureFlag, updateFeatureFlag, and archiveFeatureFlag
Development
Project Structure
bucketeer-mcp/
├── src/
│ ├── api/
│ │ └── client.ts # Bucketeer API client
│ ├── tools/
│ │ ├── list-flags.ts # List feature flags tool
│ │ ├── create-flag.ts # Create feature flag tool
│ │ ├── get-flag.ts # Get feature flag tool
│ │ ├── update-flag.ts # Update feature flag tool
│ │ ├── archive-flag.ts # Archive feature flag tool
│ │ └── index.ts # Tool exports
│ ├── types/
│ │ └── bucketeer.ts # TypeScript type definitions
│ ├── utils/
│ │ └── logger.ts # Logging utility
│ ├── config.ts # Configuration management
│ ├── server.ts # MCP server implementation
│ └── index.ts # Entry point
├── .env.example # Environment variables template
├── .gitignore
├── package.json
├── tsconfig.json
└── README.mdLinting
Run the linter:
npm run lintBuilding
Build the TypeScript code:
npm run buildTroubleshooting
Common Issues
Authentication errors: Ensure your API key is valid and has the necessary permissions
Environment ID not found: Verify the environment ID exists in your Bucketeer instance
Connection errors: Check that the BUCKETEER_HOST is correct and accessible
Logging
The server logs to stderr in JSON format. Adjust the log level using the LOG_LEVEL environment variable:
error- Only errorswarn- Warnings and errorsinfo- General information (default)debug- Detailed debug information
License
MIT
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Available Tools
5 toolsarchiveFeatureFlagC
Archive a feature flag (make it inactive)
Inputs: id (required), comment (required), environmentId.
createFeatureFlagC
Create a new feature flag in the specified environment
Inputs: id (required), name (required), variations (required), defaultOnVariationIndex (required), +5 more.
getFeatureFlagC
Get a specific feature flag by ID
Inputs: id (required), environmentId, featureVersion.
listFeatureFlagsC
List all feature flags in the specified environment
Inputs: environmentId, pageSize, cursor, tags, +5 more.
updateFeatureFlagC
Update an existing feature flag
Inputs: id (required), comment (required), environmentId, name, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for Statsig API - interact with Statsig's feature flags, experiments, and analytics
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server implementation that integrates with Unleash Feature Toggle system.21635 npm10MIT

hackle-mcpofficial
AlicenseBqualityDmaintenanceA Model Context Protocol server for Hackle API providing tools and resources for querying A/B Test data.193MIT
GrowthBook MCP Serverofficial
AlicenseBqualityBmaintenanceOfficial GrowthBook MCP server for creating flags, getting experiments, and more.1410,340 npm26MIT- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-