Skip to main content
Glama
Rutyro

cc-peer

by Rutyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cc-peer

No user-submitted related servers found.

    Related Servers

    • agentchan

      damejeras
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to communicate with each other by sending messages and waiting for replies across sessions, supporting agents like Claude Code, Codex, and Grok.
      MIT

    • interclaude

      alexgoodell
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables peer-to-peer communication between Claude Code sessions, allowing them to send messages, hand off tasks, and coordinate across worktrees without manual intervention.
      MIT

    • AgentHop

      sdyuyouth
      A
      license
      A
      quality
      A
      maintenance
      Lets your AI agent talk directly to another person's agent on a different machine. One pairing code connects them through an end-to-end encrypted relay (hosted or self-hosted), with no public IP needed; it also sends files and invites saved contacts by name.
      14
      6
      Apache 2.0

    • AgentBridge

      Joseamica
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables a coding agent to ask another person's coding agent questions across different machines, networks, and subscriptions, with revocable directional permission and a locked-down responder session enforced by configuration.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_peers and send_message have completely distinct purposes—one enumerates reachable peers, the other transmits a message and returns a reply. There is no plausible way to confuse them.

    Naming Consistency5/5

    Both names follow a clean verb_noun snake_case pattern (list_peers, send_message), with consistent, predictable verb choice.

    Tool Count4/5

    Two tools is slightly thin for the stated peer-messaging scope, but each earns its place and the surface is not padded. A minimal discovery+send pair is a reasonable design.

    Completeness4/5

    The core lifecycle—discover peers, send a message, get a reply—is fully covered. Minor gaps exist (e.g. broadcasting to multiple peers or inspecting message history), but agents can work around them by iterating over peers.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources