dibs
Related Servers
Alternatives to dibs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA 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.2,144MIT
- AlicenseNot gradedqualityAmaintenanceLocal coordination for coding agents that share a Git working tree.19 npm2MIT
- 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.13MIT
- FlicenseNot 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.-
- 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
- AlicenseAqualityAmaintenanceLocal-first shared memory and task coordination for AI coding agents. One Go binary, MCP server, markdown files you own. Hooks for Claude Code and Codex CLI (and their desktop apps).304MIT
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.