MCP bridge for MPAC: coordinate coding agents working on the same repository
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":"mpac-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.
# mpac-mcp [](https://arxiv.org/abs/2604.09744) [](https://pypi.org/project/mpac-mcp/) 📄 **Paper:** [MPAC: A Multi-Principal Agent Coordination Protocol for Interoperable Multi-Agent Collaboration](https://arxiv.org/abs/2604.09744) (arXiv:2604.09744) `mpac-mcp` is the MCP-facing bridge for MPAC — it lets MCP-aware coding clients (Claude Code, Cursor, any MCP host) participate in an MPAC coordination session without re-implementing the protocol themselves. The underlying protocol and reference runtime live in [`mpac-protocol`](https://github.com/KaiyangQ/mpac-protocol) / the [`mpac`](https://pypi.org/project/mpac/) package. It does not re-implement the coordination protocol. Instead it: - detects the current repository context - ensures a local MPAC sidecar is running - queries the sidecar for shared coordination state - exposes high-level tools to MCP-compatible coding clients All bundled smoke scripts now run against an isolated scratch workspace copied from the requested repo path, so repeated runs do not inherit stale conflicts or frozen scope from a long-lived sidecar session. ## Current scope This initial scaffold focuses on the shortest end-to-end path: - local sidecar auto-discovery / auto-start - repository-root detection - session summary query - first MCP tools: - `who_is_working` - `begin_task` - `check_overlap` - `get_file_state` - `ack_conflict` - `submit_change` - `yield_task` - `escalate_conflict` - `resolve_conflict` - `take_over_task` - a Milestone 0 validation script for "two processes share one local coordinator" - an end-to-end smoke script for "one external client + one MCP-owned task" - an end-to-end smoke script for "begin task -> submit change -> yield task" - an end-to-end smoke script for "ack -> escalate -> resolve" - an end-to-end smoke script for "suspend -> claim -> take over" ## Multi-tena…
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.