Skip to content
MCP server

Beadhive

Run cross-repository beads work and hive status for agent-driven engineering

Runs locallyStatus and history
Pricing
Open source
Platforms
CLI, self-hosted
Runs
Locally
Version
0.38.0
Listing updated
3 days ago

About Beadhive

Beadhive is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

Beadhive's bh command is the front end of a software factory that tracks work as beads: each repository is its own issue database (a hive) with a short stable prefix, and bh onboards them, keeps labels consistent and aggregates every hive into one cross-repo view. This MCP server, bh-mcp, exposes that to agents.

Issue data lives in each repo's own Dolt database under refs/dolt/data on its git remote, with config under ~/.beadhive/. The project describes seats such as planner, dispatcher, developer, reviewer, merger and warden, which a person or an agent can fill, and human-held gates that block a merge while open. Validation results are tied to the exact tree they ran on.

It is a thin orchestrator over bd, git, git-workspace, dolt and docker, and the recommended install uses Nix. The site says nothing is hosted and the repo is untouched until you ask.

Install

Run in a terminal

claude mcp add beadhive -- uvx beadhive

Add to claude_desktop_config.json

{
  "mcpServers": {
    "beadhive": {
      "command": "uvx",
      "args": [
        "beadhive"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "beadhive": {
      "command": "uvx",
      "args": [
        "beadhive"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "beadhive": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "beadhive"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "beadhive": {
      "command": "uvx",
      "args": [
        "beadhive"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "beadhive": {
      "command": "uvx",
      "args": [
        "beadhive"
      ]
    }
  }
}

What it does

Cross-repo view
Aggregate many repositories' issue databases into one.
Seats and gates
Planner to warden roles, with merge blocked while a gate is open.
Dependency graph
A git-embedded tracker computes what to do next.
Per-agent identity
Each agent works in its own worktree under its own identity.
Proven validation
Results are keyed to the exact tree they ran on.
Local only
No signup or hosted dependency.

Good for

  • See issue status across several repositories at once
  • Let agents plan, review and merge with human gates
  • Onboard a new repo into a shared label scheme
  • Gate releases on attested validation

Pricing

Open source

Open source; no hosted service

Prices change. Check beadhive.ai before you buy.

Beadhive FAQ

Is anything hosted?

The site says no signup and no hosted dependency; everything runs on your machine.

Where is issue data stored?

In each repo's own Dolt database on its git remote, not in ~/.beadhive/.

What does it depend on?

bd, dolt, gh, git-workspace and git; the managed install pins them with Nix.

Is it open source?

The site describes it as open source.

Is Beadhive free?

Yes. Beadhive is open source, so you can use and self-host it for free.

How do I add Beadhive to Claude Code?

Run this command in your terminal: claude mcp add beadhive -- uvx beadhive

What are the best alternatives to Beadhive?

The closest alternatives to Beadhive are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Beadhive

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ha MCP

    MCP server

    MCP server for managing and automating Home Assistant from AI assistants

    Runs locally
    • 8 tools
    • Open source
    • 7.9K GitHub stars
    • Productivity