tower-mcp
Related Servers
Alternatives to tower-mcp
No user-submitted related servers found.
Related Servers
- 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.-
- 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.932 PyPIPolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityBmaintenanceCoordinates multiple AI coding agents by providing a shared task board, memory, and advisory file claims, letting agents work on the same repo concurrently without duplicating work or overwriting each other.16 npm1MIT
- AlicenseAqualityCmaintenanceEnables teams to share structured, git-synced context among AI coding agents working on the same repository, including living plans, task declarations, handoff briefs, file-provenance history, and conflict detection.1230 npm3MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI coding agents to collaborate on a project by coordinating tasks, file leases, and messages through a shared hub, preventing conflicts and enabling parallel development.MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct roles, and the rich descriptions help separate the claim lifecycle (claim_intent/check_collision/release_claim/complete_claim) from intent proposals (propose_intent) and task flows. However, a couple of pairs invite confusion: heartbeat vs heartbeat_worker, and the trio claim_intent/propose_intent/check_collision all touch pre-work collision checking.
The dominant pattern is predictable verb_noun (claim_intent, release_claim, complete_claim, list_claims, send_message, accept_task, complete_task, list_tasks, request_approval, resolve_approval). A few deviations stand out—heartbeat, heartbeat_worker, pending, next_task—which break the otherwise clean convention.
20 tools is on the heavier side, but the server legitimately spans several subdomains (claims, tasks, messaging, decisions, approvals, presence), so most tools earn their place. A little redundancy exists (pending duplicates part of fetch_messages/list_tasks; two heartbeat tools), but not enough to feel bloated.
Coverage is strong: full claim lifecycle, task delegation/accept/complete with approvals, messaging, decision memory, and presence. Minor gaps remain—no explicit task-creation tool (folded into send_message with kind 'task') and no update/delete for recorded decisions.