agent-comms
Related Servers
Alternatives to agent-comms
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLocal OS for your AI Agents fleets. ——————- Enables AI agents to coordinate through a durable local board with shared state, ticket lifecycle, evidence-based approvals, and journal-woken handoffs.2Apache 2.0
- 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 AI coding agents to ask the user questions, receive written replies, share files, and hand tasks to other agent sessions — with every cross-agent request routed through human approval first. Sessions register themselves so they can be read, woken, and answered from a phone over a local-first, self-hosted setup.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables local coding agents to track sessions, exchange isolated collaboration messages, and optionally delegate coding work to Codex with Git worktree isolation and task management.602 npmMIT
- 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 gradedqualityBmaintenanceGives a hackathon team's AI coding agents and their humans a shared task board and inbox, so agents can atomically claim tasks, move them between todo/doing/blocked/done, post messages to teammates or the whole team, and read new messages plus board events since they last checked. It also exposes member and agent activity, letting multiple agents working in the same repo coordinate without duplicating work.MIT
TDQS
Scored across 8 tools
Most tools target clearly distinct operations: register session, post, read unread updates, list threads, set summary, claim/release/update task. The lease trio (claim_task, release_task, update_task) and the two read tools (read_updates vs list_threads) are adjacent in purpose but the descriptions clearly separate lease acquisition from lifecycle transitions and cursor-based reading from thread overview.
All tools share the board_ prefix with a predictable verb-first pattern (board_claim_task, board_update_task, board_release_task, board_set_summary, board_list_threads). board_register and board_post are slightly shorter but still fit the same scheme and remain perfectly readable, so there is no convention mixing.
Eight tools is well-scoped for a coordination board covering sessions, posts, reads, summaries, and task leases. Each tool maps to a distinct lifecycle step with no redundant operations.
The surface covers session registration, posting/threading, incremental reads, thread listing, summary pinning, and the full task lease lifecycle (claim, renew, release, transition). Minor gaps exist around editing/deleting posts or threads, but core workflows have no dead ends.