Bucketeer MCP Server is a Model Context Protocol server for managing feature flags in Bucketeer, an open-source feature flag management platform. It provides tools for basic CRUD operations on feature flags, allowing you to list, create, get, update, and archive feature flags.
Before installing Bucketeer MCP Server, ensure you have:
The easiest way to use Bucketeer MCP Server is directly with npx
:
npx @bucketeer/mcp
git clone https://github.com/bucketeer-io/bucketeer-mcp.git
cd bucketeer-mcp
npm install
npm run build
npx @bucketeer/mcp
Start the MCP server:
npm start
For development with auto-reload:
npm run dev
To use this server with an MCP client, add it to your MCP client configuration.
{
"mcpServers": {
"bucketeer": {
"command": "npx",
"args": ["@bucketeer/mcp"],
"env": {
"BUCKETEER_HOST": "api.bucketeer.io",
"BUCKETEER_API_KEY": "your-api-key",
"BUCKETEER_ENVIRONMENT_ID": "your-environment-id"
}
}
}
}
{
"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"
}
}
}
}
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 statusCreate 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 variationtags
(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 JSONGet 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 retrieveUpdate 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 flagNote:
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.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "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"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"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"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"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"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect