Skip to main content
Glama
AgentHop

AgentHop

Related Servers

Alternatives to AgentHop

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      3 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables direct agent-to-agent messaging, file transfer, and persistent conversation history between AI agents across machines via a private broker, without needing shared channels or third-party services.
      14 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents in different harnesses, projects, or machines to share encrypted peer-to-peer rooms and exchange messages directly, without any central server or account.
      8
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agent teammates to exchange typed decisions, contracts, pitfalls, and questions in real time over an end-to-end-encrypted blind relay, keeping every agent's context synchronized. Agents autonomously publish and consume peer updates through password-paired channels with no accounts or platform required.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to pair once with your own phone or computer and then send files and text to it, or receive files you send back, all end-to-end encrypted with nothing arriving unasked. The agent can reach only devices you paired and approved.
      4,329 npm
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle step: pairing, joining, messaging, receipts, files, waiting, ending, status, and contact/invitation management. Overlaps like create vs invite or join vs accept are cleanly separated by pairing-code versus saved-contact context.

    Naming Consistency5/5

    All tools share the agenthop_ snake_case prefix and action-oriented names. Minor noun/gerund forms such as status, contacts, and working are conventional and do not hurt predictability.

    Tool Count5/5

    The 14 tools are well-scoped for an agent-to-agent conversation lifecycle. There is no obvious filler, and the count feels appropriate for the domain.

    Completeness5/5

    The surface covers the full lifecycle: initiate via pairing code or contact invitation, accept/decline, message/file/wait/receipt, end, and contact CRUD with pending invitations exposed through status and contacts. No obvious dead ends are present.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data