Skip to main content
Glama
intershopper

Kiro Agent-Mailbox

by intershopper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Kiro Agent-Mailbox

No user-submitted related servers found.

    Related Servers

    • Swarmail

      bompus
      A
      license
      A
      quality
      A
      maintenance
      Local agent-to-agent messaging and coordination for coding sessions on one machine, through MCP and a CLI. Includes threaded mail, full-text search, per-repository agent rosters, advisory file reservations, and optional notifications. Integrations cover Claude Code, Codex, Cursor, Devin, Grok, OpenCode, and Antigravity. Standalone agents and T3 Code sessions can share the same local server.
      2
      22
      1
      MIT

    • harness-summit

      anthonyleung-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      439 npm
      MIT

    • Agent Wire

      kevinmanase
      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

    • MCP Agent Bus

      therapietech
      A
      license
      A
      quality
      A
      maintenance
      Enables multiple AI coding-agent sessions on one machine to hand tasks to each other and get results back through a shared local folder of JSON messages, with no cloud, database, or network service. Supports direct messages, broadcasts, blocking receive, and an optional headless worker that picks up, runs, and auto-replies to tasks.
      6
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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

    Resources