A
licenseNot graded
qualityC
maintenanceEnables 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.
3 npm
8
MIT
git-bug-broker
by JovianIce
Related Servers
Alternatives to git-bug-broker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityBmaintenanceEnables multiple AI tools to observe the same local project, share file changes with per-client pagination and acknowledgement, coordinate turn-based collaboration, and exchange private, broadcast, and reply messages through a local mailbox.MIT
- AlicenseNot gradedqualityCmaintenanceLocal coordination for coding agents that share a Git working tree.8 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to coordinate via authenticated task creation, claiming, messaging, and review approval over a secure local event log.-
- AlicenseNot gradedqualityBmaintenanceEnables provider-neutral durable coordination for coding agents sharing Git work, including peer discovery, durable messaging, job progress tracking, and FIFO integration authority with fenced leases.MIT
TDQS
B3.3/5.0
Scored across 9 tools
Disambiguation4/5
Each tool maps to a fairly distinct action: create (file_entry), read (get), list (query), and targeted mutations (set_status, set_title, relabel, edit_body, edit_comment, comment). The main friction is edit_body vs edit_comment, which overlap since the body is described as 'its first comment'—an agent could hesitate over which to use.
Naming Consistency3/5
Several tools follow a clean verb_noun pattern (edit_comment, set_status, set_title, edit_body, file_entry), but others are bare single words (get, query, relabel, comment). It's readable but the convention is mixed rather than predictable.
Tool Count5/5
Nine tools is well-scoped for an issue-tracker surface, covering the core lifecycle without bloat or redundancy. Each tool clearly earns its place.
Completeness4/5
Creation, reading, listing, commenting, and most update operations (status, title, labels, body, comments) are covered. The notable gap is deletion—no tool to remove an entry or a comment—though this may be intentional for an append-oriented bug tracker.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues