Coding agent-agnostic MCP hub for managing multiple 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":"central-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.
# central-mcp <p align="center"> <img src="https://raw.githubusercontent.com/andy5090/central-mcp/main/docs/logo.png?v=0.11.0" alt="central-mcp logo" width="280"/> </p> <p align="center"> <strong>English</strong> · <a href="README_KO.md">한국어</a> </p> [](https://pypi.org/project/central-mcp/) [](https://pypi.org/project/central-mcp/) [](LICENSE) **The portfolio PM for running many agent-driven projects at once.** > **All lines run through central.** Dispatch across every project, and never lose the thread of any of them. One MCP server turns any MCP-capable client (Claude Code, Codex CLI, Gemini CLI, opencode, [Hermes Agent](https://github.com/NousResearch/hermes-agent), [OpenClaw](https://github.com/openclaw/openclaw), gajae-code) into a control plane for your portfolio of coding-agent projects. Ask in natural language, and the orchestrator routes the request to the right project's agent — non-blocking, with results reported back asynchronously — then briefs you on that project's real state whenever you come back to it. ## Why Agents made it cheap to *run* four, eight, fifteen projects at once. They did nothing about *keeping track* of them. Every context switch charges a re-orientation tax — *what happened here while I was away? What state is it in? What was I about to do next?* — and nobody is playing PM. `central-mcp` is that PM: - **Dispatch** — send work to any project's agent, in parallel, and keep talking while it runs - **Pulse** — return to a project and get "what happened / where it stands / what's next", computed from the **repository itself**, so work that never went through the hub (direct commits, interactive agent sessions, manual edits) counts too - **Digest** — a fixed-format daily/weekly portfolio report, deliverable to chat by a resident agent or a …
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.