Skip to main content
Glama
cerberusgamelabs

InterAgentMail

by cerberusgamelabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to InterAgentMail

No user-submitted related servers found.

    Related Servers

    • set-agent-comm

      tatargabor
      A
      license
      Not graded
      quality
      B
      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

    • CC2CC

      non4me
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables file-based agent-to-agent communication between Claude Code instances on the same machine, using MCP channels and plain JSON files.
      4 npm
      14
      MIT

    • pigeonpost

      bekirdag
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.
      MIT

    • dsh-agent-mailbox

      blairlaird
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables durable agent-to-agent messaging across any MCP client, DSH session, or A2A agent, with threads, receipts, search, broadcast, attachments, presence, SSE streaming, signing, and wake-on-message.
      MIT
    • hauddy by Hauddy

      hauddyofficial

      Hauddy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.
      3
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, but timer_clear vs timer_cancel and the timer_set_team/timer_set_for/timer_set trio could cause selection hesitation. Descriptions generally resolve the ambiguity.

    Naming Consistency4/5

    All tools share the iam_ prefix and snake_case convention, and most follow verb_noun. A few noun-style names like iam_inbox and compound names like iam_timer_set_for break the strict pattern slightly.

    Tool Count3/5

    23 tools is on the heavy side for an MCP server, though each domain cluster (mail, chat, timers, team) is internally coherent. The count feels manageable but exceeds the typical well-scoped range.

    Completeness4/5

    Mail, chat, timer, and team management all have core lifecycle coverage: send/read/reply/archive, join/post/tail/leave, set/list/cancel/snooze, and add/remove member. Minor gaps like team listing or message search exist but are not blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources