Beadhive — Claude Code MCP server: what it does, how to install
Aggregates distributed beads issue tracking across multiple repositories into one workspace for coding agents.
claude mcp add beadhive -- uvx beadhiveWhat Beadhive does
Beadhive operates as a central bridge across decentralized issue databases powered by beads. Every tracked repository maintains an independent task ledger called a hive. The MCP server gives agents visibility into cross-project work queues without forcing you to clone every repository locally.
Behind the scenes, the tool orchestrates external utilities such as bd, git, dolt, docker, and git-workspace. It is an orchestrator, not a standalone tracker. Task records avoid your local ~/.beadhive/ directory; instead, issues stay in Dolt databases under refs/dolt/data on remote Git branches.
Running bh requires external tools like bd and dolt on your machine, so installing via PyPI leaves binary dependency management up to you.
What it helps with
- track beads issues across several repositories simultaneously
- register new project repos into a shared hive workspace
- standardize issue labels across separated databases
- inspect issue lists without local checkouts of source trees
Example prompts for the agent
- List all tasks ready for work across registered hives using bh
- Register github/org/core-service as a new beads hive
- Check current cross-repo issue status via Beadhive
How to install Beadhive
Platform CLI
claude mcp add beadhive -- uvx beadhiveuvx runs the command named after the package; if the README names another one, use uvx --from beadhive <command>
Platform CLI
codex mcp add beadhive -- uvx beadhiveuvx runs the command named after the package; if the README names another one, use uvx --from beadhive <command>
Config file
{
"mcpServers": {
"beadhive": {
"command": "uvx",
"args": [
"beadhive"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from beadhive <command>
Config file
{
"servers": {
"beadhive": {
"type": "stdio",
"command": "uvx",
"args": [
"beadhive"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from beadhive <command>
Platform CLI
gemini mcp add beadhive uvx beadhiveuvx runs the command named after the package; if the README names another one, use uvx --from beadhive <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Beadhive
How to install Beadhive in Claude Code?
Run claude mcp add beadhive -- uvx beadhive in your terminal. You must also have supporting CLI tools like bd and dolt available on your system.
Where are issue records stored?
The ~/.beadhive/ path stores only local configuration and cache files. Actual task data lives directly inside the remote Git repositories under refs/dolt/data via Dolt.
What does Beadhive do?
It coordinates multiple beads issue trackers into a unified interface. Agents can query and update tasks across several projects from a single session.
