ACDP
Related Servers
Alternatives to ACDP
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI coding agents to coordinate by sharing environment snapshots and diffs, surfacing overlapping work, exchanging debug-session messages, handing off tasks, and enforcing policy preflight checks.-- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.473 npm8MIT
- AlicenseNot gradedqualityCmaintenanceA Redis-backed MCP server that enables multiple AI agents to communicate, coordinate, and collaborate while working on parallel development tasks, preventing conflicts in shared codebases.20MIT
- AlicenseNot gradedqualityAmaintenanceEnables multiple AI agents using MCP-compatible clients to collaborate in parallel on the same project across one or more machines, with direct messaging, a shared task board, atomic file/folder locking, presence tracking, and a live web dashboard.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for coordinating multiple AI agents across developers and vendors with a shared job board, per-file locking, and live project context.5AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for AI coding agents to coordinate on shared repositories, enabling task claiming, conflict detection, and plan management in real-time.36 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct action: locking, unlocking, checking locks, requesting commits, notifying sync, listing agents, starting/connecting to servers, and checking connection status. No two tools have overlapping purposes.
Most tools follow a verb_noun pattern (e.g., lock_files, release_files, list_agents, request_commit). Minor deviations like connection_status (noun_noun) and start_local/connect_remote (verb_adjective) break the pattern slightly, but the naming remains readable and predictable.
With 9 tools, the set is well-scoped for a coordination server. Each tool serves a clear purpose without redundancy, fitting comfortably within the ideal 3-15 range.
The tool set covers the core workflow: file locking (lock_files, release_files, check_locks), commit request and notification (request_commit, notify_sync), and agent/connection management (list_agents, start_local, connect_remote, connection_status). Minor gaps exist, such as no explicit approve_commit or disconnect tool, but these are likely handled outside the tool surface.