LLM Bus
Related Servers
Alternatives to LLM Bus
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for coordinating multiple AI agents across developers and vendors with a shared job board, per-file locking, and live project context.5AGPL 3.0

STMAofficial
FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI coding agents to coordinate by sharing environment snapshots and diffs, surfacing overlapping work, exchanging debug-session messages, handing off tasks, and enforcing policy preflight checks.-- AlicenseAqualityBmaintenanceShared versioned state for multi-agent AI workflows. An MCP server.52MIT
- -licenseNot gradedqualityBmaintenanceAn MCP server that provides coordination tools (claim, release, broadcast, state) for concurrent coding agents working on a CRDT-merged shared filesystem, ensuring no edits are lost and enabling collaborative task completion.-
- AlicenseNot gradedqualityBmaintenanceA shared memory and coordination server for multiple AI coding agents, built on the Model Context Protocol (MCP).5MIT
- AlicenseAqualityDmaintenanceA filesystem-based MCP server for AI coding agents to coordinate work across git worktrees by claiming files, checking for conflicts, and logging progress without affecting the repository's git history.5MIT
TDQS
Scored across 27 tools
Each tool has a clearly distinct purpose: admin tools for project management, task tools for workflow, sequence tools for numbering, communication tools for posts, and utility tools for awareness. No two tools overlap in intent.
Names follow a consistent verb_noun or prefix_noun pattern (e.g., admin_provision, task_create, list_participants), with minor exceptions like 'whoami' vs. 'who_is_active' and 'whats_new' vs. 'whoami'—mostly predictable.
27 tools is relatively high, covering project admin, tasks, sequences, leases, and communication. While each tool serves a specific need, the set could likely be consolidated, e.g., merging some sequence tools or reducing admin variants.
The server covers core operations for project collaboration: admin provisioning, task lifecycle (create, assign, start, block, resolve, ship), sequence management, leases, and communication (post, ack, read). Minor gaps exist (e.g., no direct message or broadcast), but the surface is largely complete for its domain.