local-agent-board
Related Servers
Alternatives to local-agent-board
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables local AI coding agents to message each other on one machine using a durable SQLite mailbox and live-ask tools.93MIT
- AlicenseBqualityBmaintenanceEnables AI agents from different frameworks to communicate asynchronously via a persistent SQLite-backed bus, with doorbell wakeups for sub-second notifications and full message history.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to exchange messages through a local-first SQLite-backed bus with inboxes, group work queues, acknowledgements, retries, and scheduling over loopback.MIT
- FlicenseNot gradedqualityDmaintenanceEnables multiple AI agents to communicate and coordinate via a shared SQLite-backed message log, supporting directed messages, broadcasts, and session discovery.-
- AlicenseNot gradedqualityCmaintenanceEnables multiple concurrent CLI coding agents and a human operator to coordinate through a local SQLite-backed message bus with active turn wakeup, busy-session steering, mention-gated channels, fan-out messaging, and reply barriers.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange structured work items with an auditable lifecycle, supporting send, acknowledge, block, complete, and cancel operations via a shared SQLite-backed inbox.35 npm2Apache 2.0
TDQS
Scored across 7 tools
Each tool maps to a clearly distinct action in one of two domains: lease management (lock, renew, unlock, lock_status) and messaging (post, inbox, ack). No two tools can reasonably be confused for the same operation.
Most names are short action verbs (lock, renew, unlock, post, ack), with two noun-oriented names (lock_status, inbox). The convention is mostly predictable but not uniformly verb_noun.
Seven tools is well-scoped for a local agent coordination board. Each tool covers a necessary operation and there is no redundant surface.
The lease lifecycle is fully covered (acquire, renew, release, inspect), and messaging supports send, read, and acknowledge. Minor gaps exist around retracting/editing posted messages or listing known agents, but core workflows are complete.