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.
      5 npm
      6
      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.
      3 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
      3
      MIT

    • Srift-Transfer

      srivardhan113
      F
      license
      Not graded
      quality
      B
      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.
      57
      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

    A3.8/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have distinct purposes: conversation initiation (create/join/invite/accept), messaging (say/working/wait/bye), file transfer, and contact management. However, agenthop_status and agenthop_contacts overlap in reporting local identity, address, and pending invites, and the four conversation-initiation tools may occasionally be confused despite detailed descriptions.

    Naming Consistency4/5

    All tools use a consistent agenthop_ prefix with snake_case, and there is no mixed casing or naming style. The pattern is not strictly verb_noun throughout (status and contacts are nouns, working is a gerund), but it remains predictable and readable.

    Tool Count5/5

    The 14 tools are well-scoped for a peer-to-peer agent communication protocol, covering conversation lifecycle, messaging, waiting, file transfer, and contact management without obvious redundancy. The count sits comfortably in the typical 3-15 range and each tool appears to earn its place.

    Completeness4/5

    Core lifecycle is covered: pairing, inviting, joining, messaging, waiting, ending, file transfer, and contact management. Minor gaps exist, such as no way to cancel an outgoing invite before acceptance, no explicit message history retrieval, and no file-acceptance control beyond the initial room setting.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources