Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
An MCP server that lets two (or more) AI agents collaborate on the same git repository without stepping on each other. Each agent declares what it's building before it builds, sees what its partner has claimed, and detects conflicts when work lands — all coordinated through the repo itself, with no lock server and no requirement that both agents be online at once.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| claim_overlap | declared-path intersection (intent, path-aware). |
| merge_conflict | a real git merge-tree dry-run merge (textual). Catches |
| Variable | Description | Required |
|---|---|---|
| AGENTSYNC_BOARD_REPO | Configuration value read at startup. | Optional |
| AGENTSYNC_AGENT_ID | Configuration value read at startup. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
The `bbmd` cli should be the superior to MCP when used by AI agents.
Call another mcp client from your mcp client. Delegate tasks, offload context windows. An agent for your agent
Agent Interviews is an AI-powered research platform designed to conduct qualitative interviews an...
İzmir toplu taşıma verilerine erişim sağlayan bir Model Bağlam Protokolü (MCP) sunucusu, AI asistanlarının şehir ulaşım verilerini ve analizlerini