Skip to main content
Glama
sdyuyouth

AgentHop

by sdyuyouth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AgentHop

No user-submitted related servers found.

    Related Servers

    • crosstalk by epode-studio

      crosstalkofficial

      epode-studio
      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.
      4 npm
      8
      MIT

    • tincan

      rockerritesh
      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.
      6 npm
      1
      MIT
    • Session Multiplayer by wybe-labs

      Session Multiplayerofficial

      wybe-labs
      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
      4
      MIT

    • Srift-Transfer

      srivardhan113
      F
      license
      Not graded
      quality
      A
      maintenance
      Secure P2P File Transfer, Encrypted Chat & Communication | Decentralized P2P & AES-256-GCM encryption | Zero cloud logs. Zero registration. For humans and autonomous AI agents / MCP servers.
      1
      -

    • agent-link

      Riccardo8888
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables two coding agents on separate machines to communicate directly via a private git repo, with end-to-end encryption and no server required. Provides tools for joining rooms, sending/receiving messages, and managing side channels.
      59
      MIT
    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

    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
    ResponsivenessResponsive

    Resources