agent-mailbox
Related Servers
Alternatives to agent-mailbox
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.9MIT
- FlicenseNot gradedqualityCmaintenanceGlobal mailbox and address book for AI agents, enabling asynchronous messaging across machines without requiring simultaneous online presence.-
- AlicenseAqualityAmaintenanceEnables AI agents to send and receive structured, cryptographically-verifiable messages, with tools for inbox management, task delegation, and agent discovery.12118 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables direct agent-to-agent messaging, file transfer, and persistent conversation history between AI agents across machines via a private broker, without needing shared channels or third-party services.3 npm1MIT
- FlicenseCqualityDmaintenanceA lightweight messaging system that enables real-time communication between different AI agents through a shared, file-based message queue. It provides tools for sending, checking, and broadcasting messages to facilitate coordination across isolated project namespaces.81-
- AlicenseNot gradedqualityAmaintenanceProvides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.1MIT
TDQS
Scored across 9 tools
mailbox_send with 'all' overlaps significantly with mailbox_broadcast, creating redundant paths for the same action. mailbox_check and mailbox_list both involve fetching messages, though check ack semantics and list filtering differentiate them. Overall boundaries are mostly clear but these overlaps introduce real selection ambiguity.
All tools share a consistent mailbox_ prefix and snake_case style, with most names following a verb form like check, register, send, reply, list, and wait. The non-verb names 'done' and 'whoami' deviate slightly, and send/broadcast are near-synonyms, but the overall pattern is coherent and predictable.
Nine tools is well-scoped for a mailbox domain, covering registration, sending, receiving, replying, listing, waiting, and completion. Each tool earns its place and the count does not feel bloated or thin.
The tool set covers the core mailbox lifecycle: register, send, receive, reply, list, wait, and mark handled, so typical agent communication flows are supported. Missing explicit archive/delete operations and unread/read state controls are minor gaps that agents can work around.