dibs
Related Servers
Alternatives to dibs
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceA coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.412,240MIT
- AlicenseNot gradedqualityCmaintenanceLocal coordination for coding agents that share a Git working tree.6 npm2MIT
- AlicenseAqualityCmaintenanceEnables parallel AI coding agents to claim files atomically, detect and prevent workspace collisions, and receive deterministic zero-latency safety verdicts on destructive shell commands without any network egress. It also provides autonomous wave dispatch, worker recovery, and completion verification for multi-agent workflows via a shared coordination board.7MIT
- AlicenseBqualityBmaintenanceEnables multiple coding agents sharing one repository to coordinate their work through time-limited directory and file leases, an enforced pre-tool-use hook, shared presence tracking, messaging, and an audit history, so they never edit or run each other's files concurrently.1558 PyPIMIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.MIT
TDQS
Scored across 8 tools
Each tool addresses a distinct coordination task—claim management, status overview, lessons, and notes—with no overlap. An agent can easily tell which tool to use for claiming, checking, releasing, or communicating.
All tools share the 'dibs_' prefix and use snake_case, but 'dibs_status' and 'dibs_notes' are nouns while most others are verbs (release, check, claim, etc.). This minor inconsistency is easy to overlook given the clear prefix and short names.
With 8 tools, the server is well-scoped for its purpose: 4 for claim/status management, 2 for lessons, and 2 for notes. Each tool earns its place without redundancy or bloat.
The tool surface fully covers the coordination domain: claim, release, check, status, lesson add/search, and note broadcast/read. There are no obvious missing operations—manual expiry is unnecessary because leases auto-expire, and release complements claim.