postbag
Related Servers
Alternatives to postbag
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code, Codex CLI and Antigravity (Gemini) agents to exchange messages that are pushed live into each other's open sessions, with mail_send, mail_check and mail_peers tools so no agent has to poll. Mail can also be bridged over SSH between machines with no shared filesystem.3908 npmMIT
- AlicenseAqualityAmaintenanceWalkie-talkies for AI coding agents: Claude Code, Codex, Cursor and any MCP client message other developers' agents directly, peer to peer over HyperDHT and end-to-end encrypted. No server, no account. Pair once with a 6-digit verify code; offline peers get messages through a sealed mailbox on the DHT. Tools: send_message, read_inbox, list_messages, list_peers, get_status.5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables peer-to-peer messaging and coordination between Claude Code sessions via a shared mail server, with tools for roster, ask, dm, inbox, board, and claim.1 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables one AI coding agent to discover, read, message, and wait on other agent sessions across Codex threads and Claude Code or Claude Desktop sessions, while logging every send as a local receipt that can be audited later.3 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code, Codex and opencode sessions on the same machine to message each other live over a local pipe, with threaded replies and offline queuing, and to delegate or spawn one another as background subagents. Messages persist in SQLite and any running server can take over as broker, so peers stay reachable without a daemon.18 npm3MIT
- FlicenseAqualityBmaintenanceEnables Claude and Codex sessions on the same host to communicate across different session systems via shared SQLite rooms, with named participants, durable ordered messages, offline delivery, and wait-based message handling.42-
TDQS
Scored across 5 tools
Each tool has a distinct resource/action: join/leave manage peer registration, send/read manage letters, and bags inventories the bag state. The descriptions clarify subtle identity and lifecycle semantics without making tools overlap in purpose.
All tools use the postbag_ prefix and snake_case, which is highly consistent. The only minor deviation is postbag_bags, which is a noun rather than a verb like the other action-oriented names.
Five tools are well-scoped for a peer messaging/coordination server. Join, leave, send, read, and inventory cover the essential operations without bloat or obvious thinness.
The surface covers registration lifecycle, message sending/reading, and bag/peer inventory, including implicit bag creation via join. Minor gaps exist around explicit bag deletion or history clearing, but agents can work around them.