Local SQLite-backed MCP bus for peer coding agents
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-bus-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.
<p align="center"> <img src="https://raw.githubusercontent.com/alessandrobologna/agent-bus-mcp/pypi-assets/.pypi-assets/site__public__home-hero__agent-bus-home-hero-readme.jpg" alt="Agent Bus MCP website hero illustration showing local coding agents coordinating through a shared message bus." width="960" /> </p> # Agent Bus MCP Agent Bus MCP is a shared local inbox for AI coding agents. Use it when you want Codex, Claude Code, Gemini CLI, OpenCode, Cursor, or another MCP-capable tool to work on the same task without copy-pasting summaries, losing context after restarts, or scattering coordination across scratch files. Under the hood, Agent Bus MCP is a stdio MCP server backed by SQLite. Agents create named topics, join with stable peer names, send and receive messages through `sync()`, and resume from server-side cursors. The result is a durable, searchable record of handoffs, reviews, and sidecar work that stays on the local machine. > [!TIP] > Prefer the polished product and docs front door? Visit [agentbusmcp.com](https://www.agentbusmcp.com) > for the live website, then use this README and [`docs/`](docs/README.md) when you want the > repo-native setup, reference, and implementation details. ## Why use Agent Bus MCP? Multi-agent coding breaks down when every tool keeps its own memory. One agent implements, another reviews, a sidecar investigates, and the coordination ends up in pasted summaries, terminal logs, or repo scratch files. Agent Bus MCP gives those agents one shared place to coordinate: - **Handoffs stay readable.** Each task gets a named topic with one ordered message stream. - **Agents keep their identity.** A reviewer, implementer, or sidecar can reconnect with the same peer name. - **Restarts do not erase progress.** Server-side cursors remember what each agent has already seen. - **History stays inspectable.** Use the CLI or Web UI to replay, export, and search past coordination. - **Everything stays local.** The bu…
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.