Ext Ops Panel
Open dashboard
Comparison

Beadhive vs io.github.selfagency/beans-mcp

Beadhive is an MCP server published by beadhive. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.selfagency/beans-mcp is an MCP server published by selfagency. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceBeadhiveio.github.selfagency/beans-mcp
Official MCP Registry Listed
Version: 0.30.0
Downloads/month (PyPI): 2 997
Downloads/week (PyPI): 1 365
Forks (GitHub): 5
Stars (GitHub): 28
Not marked · First seen
Listed
Version: 0.1.4
Downloads/month (npm): 199
Downloads/week (npm): 36
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Beadhive vs io.github.selfagency/beans-mcp
FactBeadhiveio.github.selfagency/beans-mcp
Marketplaces that list it11
Stars (GitHub) (differs)28 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last release (differs)2026-10-24Not published
Where it runs (differs)On your machine (beadhive)On your machine (@selfagency/beans-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/beadhive/beadhivegithub.com/selfagency/beans-mcp
Changes in the last 7 days (differs)140
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Beadhive

In its own words, on Official MCP Registry:

Manage cross-repository beads work, hive status, and Beadhive workflows through bh-mcp.

io.github.selfagency/beans-mcp

In its own words, on Official MCP Registry:

Interact with the Beans CLI issue tracker agentically

How to run each

Beadhive As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio beadhive -- uvx beadhive

io.github.selfagency/beans-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio beans-mcp -- npx -y @selfagency/beans-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Beadhive · What it can do: io.github.selfagency/beans-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built