io.github.shafty023/agent-maildir
Related Servers
Alternatives to io.github.shafty023/agent-maildir
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables durable, queryable multi-agent coordination with non-blocking peer messaging, task leases, and campaign-governed collaboration across sessions.59MIT
- AlicenseNot gradedqualityCmaintenanceProvides a mail-like coordination layer for coding agents, enabling them to register identities, exchange messages through inbox/outbox, search threaded history, and declare advisory file reservations to prevent conflicts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agent sessions running under different coding harnesses on one machine to message each other and automatically wake idle receivers so they read the mail and reply. It stores all state as plain files under a home directory, with no daemon, network, or account required.67 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agent hosts to exchange durable, local sender/receiver messages through a SQLite mailbox exposed as MCP tools (connect, send, receive, reply, ack, status, disconnect), so a coordinator can dispatch commands and an executor can return results without model polling while idle. A configured host wake adapter is still required to turn an incoming event into an Agent turn.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding-agent sessions on the same machine to collaborate locally and durably by exchanging requests, replies, and task results through an authenticated loopback server with SQLite-backed storage, joined via CLI or an MCP stdio bridge. It also handles message delivery by priority and wait time, deduplicates idempotent sends, enforces task versioning, and preserves artifacts by content hash.12 npmApache 2.0
- 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
TDQS
Scored across 7 tools
Most tools map cleanly to distinct mailbox operations: status, join, bind, inbox, read, ack, and publish. The closest overlap is mailbox_join versus mailbox_bind, since both attach the session, but the descriptions distinguish registering a role from binding an existing agent id.
All tools use a clear mailbox_ prefix and consistent snake_case, making the namespace predictable. The second token mixes verbs (join, bind, read, ack, publish) with nouns (status, inbox), which is a minor deviation but still readable.
Seven tools is well-scoped for an agent mailbox server, covering setup, messaging, and acknowledgement without obvious filler. Each tool appears to earn its place in the workflow.
The core lifecycle is covered: join/bind a session, send messages, list unread messages, read full messages, and acknowledge/archive them. Minor gaps remain, such as no explicit leave/unbind operation, no way to list acknowledged/archived messages except by known id, and no visible management of the orchestrator lease mentioned in status.