Skip to main content
Glama
iambashar

agent-intercom

by iambashar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agent-intercom

No user-submitted related servers found.

    Related Servers

    • WokiToki

      pandeyvishwas51-oss
      A
      license
      A
      quality
      A
      maintenance
      Walkie-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.
      5
      Apache 2.0

    • agent-bridge

      rennerdo30
      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.
      19 npm
      3
      MIT

    • 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

    • Agent Link

      Brandon-Gottshall
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      0
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools map to clearly distinct actions: sending mail, checking/consuming inbox, and listing available peers. There is no overlap—mail_send writes, mail_check reads, and mail_peers is explicitly read-only. An agent can pick the right tool without hesitation.

    Naming Consistency5/5

    All tools follow the exact same mail_<verb> pattern: mail_send, mail_check, mail_peers. The convention is predictable, readable, and consistent throughout.

    Tool Count5/5

    Three tools exactly cover the minimal inter-agent mail model: send, receive, and discover recipients. There is no redundancy and no obviously missing core operation for this scope.

    Completeness4/5

    Core lifecycle is covered—compose/send, read/consume, and recipient discovery. Minor gaps exist: there is no tool to retrieve previously read (consumed) mail or view a sent/outbox history, though agents can work around this by acting on messages immediately or saving IDs.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive

    Resources