Coordination service for multi-engineer agent teams (HTTP API + MCP + dashboard)
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":"coord-mcp-server","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.
# Multi-Agent Team Coordination [](https://pypi.org/project/coord-mcp-server/) [](https://pypi.org/project/coord-mcp-server/) [](https://github.com/amittell/coord/actions/workflows/ci.yml) [](./LICENSE) `coord` is a small coordination layer for teams running multiple agent sessions against the same codebase. It gives Claude Code, Codex CLI, and Cursor a shared source of truth for active file/module claims so agents can check, claim, and release work before they step on each other. Agent sessions keep their claims alive implicitly via activity pings; operators can extend a specific claim over HTTP (`POST /claims/{id}/extend`). **This repo IS the coordination service.** You run one instance of it (locally during development, or as a container in whatever infra your team already uses) and point your application repos at it with `coord init`. The application repos you coordinate live elsewhere. The stack is intentionally simple: - FastAPI HTTP API (`coordination.main:app`) for claims, conflicts, ownership config, and dashboard access - SQLite storage with WAL enabled - MCP stdio bridge (`coord-mcp`) so editor/CLI tools can talk to the service as native tools - Shipped as a container image so you can deploy it on any infra that runs containers - Integration templates for `CLAUDE.md`, `AGENTS.md`, pre-push hooks, and CI ## Docs - `docs/quickstart.md`: fastest path from clone to first successful claim - `docs/getting-started.md`: fuller install + rollout guide - `docs/usage-guide.md`: day-to-day workflow for engineers and agent sessions - `docs/architecture.md`: component model, request flow, and scaling notes - `docs/api-reference.md`: endpoint reference and example payloads -…
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.