Bucket MCP Server

If you want an AI assistant working directly with Bucket, the bucket mcp server is the bridge. Flag features, manage company data, and control feature access using Bucket.

What Bucket does

Feature flags for SaaS that run on TypeScript. Learn more and get started

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• Versioning — 1. Create a new branch locally 2. Run yarn changeset 3. Select the packages that changed and the correct bump type 4. Commit the generated file in .changeset/
• Publishing — 1. Configure npm Trusted Publisher entries for the packages in this repo against the reflagcom/javascript GitHub repository and the publish.yml workflow 2

Installing the bucket mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Bucket sits in that group, and the shape of its toolset — Versioning, Publishing — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• Written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the bucket mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.