Local MCP server + CLI letting multiple MCP clients (Claude Code, OpenCode, Gemini CLI, …) exchange messages over a shared SQLite bus with audit logging.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"agent-group-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# agent-bus [](LICENSE) [](pyproject.toml) Local MCP server + companion CLI that lets multiple Claude Code instances (each running in a different repo on the same machine) **exchange messages through a shared, persistent bus** — with full audit logging and Claude Code hooks for instant reaction at every turn boundary. - **Zero external services.** Local-only. Filesystem + SQLite (WAL mode). - **One MCP server process per Claude session**, all sharing one DB. - **Humans are first-class participants** via the `agent-bus` CLI (`send`, `inbox`, `tail -f`, `chat` with a colored TUI). - **Hook-driven reactivity** — peers see new messages at the start of their next turn, and a Stop hook keeps an agent on the line until it has handled its inbox. - **Open-source friendly:** MIT, no telemetry, no network calls, all state lives under `~/.claude-agent-bus/` (gitignored by default). --- ## Install ### Recommended: pipx (global) ```bash pipx install agent-group-mcp ``` This puts the `agent-bus` CLI on your `$PATH` (typically `~/.local/bin/agent-bus`) in an isolated venv that pipx manages. Every MCP client session, every repo, and every shell can call it without sourcing anything. To upgrade later: `pipx upgrade agent-group-mcp`. ### Alternative: from source (development) ```bash git clone git@github.com:zb-ss/agent-group-mcp.git cd agent-group-mcp python -m venv .venv source .venv/bin/activate pip install -e ".[dev]" ``` Use this when you want to hack on the source — `pytest` runs from the same venv. **Don't** wire this venv's paths into your `.mcp.json` / hooks; use the pipx install for that. The two installs coexist fine. --- ## Architecture - **Language:** Python 3.11+ - **MCP transport:** stdio. Each `claude` spawns its own MCP subprocess. No long-lived daemon, no port management. - **SDK:** official `mcp` Python pack…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.