Skip to main content
Glama

Related Servers

Alternatives to Kiro Agent-Mailbox

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding-agent sessions running on one machine to exchange threaded mail over a local MCP endpoint, with full-text search, per-repository agent rosters, and advisory file reservations so concurrent sessions can coordinate instead of colliding. Sessions can also be woken when mail arrives, and reach the same tools through the paired CLI.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents such as Codex and Claude Code to exchange durable, locally stored messages through shared MCP tools for listing enrolled recipients, sending and replying to messages, reading pending inbox items, acknowledging receipt, and checking message status. Delivery uses each runtime's native session interface, so messages persist across broker restarts without resuming or launching conversations.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local agent-to-agent messaging between Claude Code sessions via file-based channels, with a registry, MCP tools and CLI for sending, reading, and tracking messages.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    register, list_agents, send_message, and reply each target a distinct action. However, check_inbox and check_replies overlap conceptually, since replies are described as arriving in the same inbox with type="reply", making it unclear why they require separate tools.

    Naming Consistency4/5

    Four tools follow a clear verb_noun pattern (list_agents, send_message, check_inbox, check_replies), while register and reply are bare verbs. Minor deviation but overall predictable and readable.

    Tool Count5/5

    Six tools is well-scoped for an agent messaging system, covering registration, discovery, sending, receiving, replying, and reply-checking without redundancy.

    Completeness4/5

    The core message lifecycle (register, list, send, receive, reply, check replies) is well covered. Minor gaps exist: no deregistration, no broadcast/multi-recipient send, and no way to mark a message handled besides replying.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues