agentsync
Related Servers
Alternatives to agentsync
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.7 npm2MIT
- AlicenseNot gradedqualityBmaintenancePrevents AI coding agents from conflicting by coordinating file claims and resolving conflicts in real-time across multiple sessions.61 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.8MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to coordinate exclusive file locks and detect semantic collisions across shared repositories, preventing silent overwrites and merge conflicts.64MIT
- AlicenseNot gradedqualityCmaintenanceEnables two AI coding agents sharing a single git checkout to coordinate by claiming files, posting and reading intent on an append-only board, and inspecting real git diffs so they avoid silent collisions. Also serves a local dashboard for watching both agents' claims, working tree, board entries, and commits.MIT
TDQS
Scored across 9 tools
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.
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.
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.
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.