A
licenseNot graded
qualityB
maintenanceEnables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.
3 npm
2
MIT
agentsync
Related Servers
Alternatives to agentsync
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenancePrevents AI coding agents from conflicting by coordinating file claims and resolving conflicts in real-time across multiple sessions.55 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI coding agents to collaborate on the same Git repository without conflicts through isolated worktrees, file locking, automated test verification, and a serialized merge queue.1 npm6MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to coordinate exclusive file locks and detect semantic collisions across shared repositories, preventing silent overwrites and merge conflicts.-
- AlicenseNot gradedqualityBmaintenanceCoordinates multiple AI coding agents by providing a shared task board, memory, and advisory file claims, letting agents work on the same repo concurrently without duplicating work or overwriting each other.12 npm1MIT
- AlicenseNot gradedqualityAmaintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.MIT
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation4/5
Most tools have clearly distinct purposes, with only minor overlap between provision and add_collaborator (both can add collaborators, but provision is for first-time setup) and between update_status and finish (both can mark done, but finish also opens a PR). The descriptions explicitly call out these differences, reducing ambiguity.
Naming Consistency3/5
Tool names mix verb_noun patterns (add_collaborator, check_conflicts, update_status) with bare verbs (provision, claim, release, finish) and one noun (history). While still readable, the naming convention is not consistent across the set.
Tool Count5/5
With 9 tools covering the full collaboration workflow (setup, claiming, surveying, conflict checking, status updates, release, finish, and history), the count is well-scoped for the server's purpose and does not feel padded or incomplete.
Completeness4/5
The tool surface covers the core lifecycle: provision and add_collaborator for setup, claim for staking work, survey and history for state visibility, check_conflicts for verification, and update_status/release/finish for progress and completion. Minor gaps exist, such as no direct way to view or edit your own claim details without using survey or re-claiming, but these are workaroundable.
Maintenance
ActivitySlowing
ResponsivenessNo issues