Quilt
Related Servers
Alternatives to Quilt
No user-submitted related servers found.
Related Servers
- 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.2 npm7MIT

cafecitoofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to coordinate on a shared repository using commutativity-proven parallel landing and regenerative merge, avoiding rebase conflicts through symbol-level leases.Apache 2.0- AlicenseBqualityAmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables multiple AI agents to collaborate on the same git repository by coordinating work via a shared claims branch, detecting file conflicts before they happen.943 PyPIPolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to coordinate exclusive file locks and detect semantic collisions across shared repositories, preventing silent overwrites and merge conflicts.-
- AlicenseNot gradedqualityBmaintenanceMultiplayer coordination for AI coding agents: Claude Code, Codex CLI and Cursor share one room per repository. An agent claims a path glob before it edits and a conflicting claim is refused at claim time, so collisions are prevented rather than resolved at merge. Metadata only — source code and diffs never leave the machine.MIT
TDQS
Scored across 12 tools
Most tools have distinct roles: start_session, claim/release, preview_mine/commit_mine, and quilt_edit/quilt_write are clear. However, get_status, get_my_changes, and get_conflicts overlap somewhat since get_status already covers ownership and collisions, which could cause misselection between the overview and specialized views.
The names are consistently snake_case and mostly verb-first, with clear pairs like claim/release and escalate/resolve. Minor deviations exist: bare imperative verbs sit alongside get_* noun-object names, and quilt_edit/quilt_write use a different prefix pattern, but the naming remains predictable overall.
Twelve tools is well-scoped for the multi-agent collaboration domain. Each tool maps to a distinct workflow step—session setup, inspection, claiming, editing, committing, and conflict resolution—without obvious bloat.
The set covers the full lifecycle: start a session, inspect ownership, claim files, edit/write, preview, commit, resolve conflicts, and escalate. Minor gaps like no explicit revert/abandon-changes tool exist, but agents can work around them with release and raw git operations.