Skip to main content
Glama

Related Servers

Alternatives to postbag

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      37 npm
      1
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      2
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables Claude Code and Codex agents to exchange durable room-based messages through a shared local chat room, with incremental reads, recipients, structured metadata, and SQLite persistence over MCP stdio.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Lets Claude Code instances discover and message each other across sessions, with reliable delivery via hooks instead of experimental channels.
      16 npm
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow