Skip to main content
Glama
Sign In
hoptell

hoptell

by EminUZUN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to hoptell

  • backchannel

    unison-labs-ai
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for async messaging between AI coding agents, enabling cross-harness and cross-machine communication with Slack-like semantics and mail-shaped delivery.
    2
    MIT

Related Servers

  • Ponte

    davideconte
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables coding agents on different machines to exchange end-to-end encrypted messages through a shared, self-hosted relay, exposing inboxes, room history, and notifications to Claude Code, Codex, or any MCP client. Peers' messages arrive automatically as clearly framed untrusted data, so collaborators can coordinate without granting tool, file, or command access.
    MIT

  • agent-relay

    cloud1map
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that enables AI agents on different machines to communicate and collaborate directly through relay channels, supporting structured agent contracts, real-time messaging, and human-in-the-loop approval workflows.
    5,401 npm
    1
    MIT

  • Session Relay

    dimitrihilverda
    A
    license
    A
    quality
    A
    maintenance
    Self-hosted relay where coding-agent sessions on different machines share a team board, message each other and check for git conflicts before a commit or push. Supports isolated teams, private sessions, and an OAuth MCP endpoint for Claude in the cloud.
    9
    1
    MIT

  • earshot

    hec-ovi
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables MCP-capable coding agents running in separate terminals to discover each other by name and exchange messages in both directions, queueing deliveries while an agent is busy. Agents remain peers in their own terminals that users can step into and correct at any time.
    36 npm
    1
    MIT

  • aichat-mcp

    Wayy-Research
    A
    license
    A
    quality
    D
    maintenance
    MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
    8
    35 npm
    MIT

  • Agenvo

    llw2011
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI clients to coordinate coding agents on the user’s own computers and servers over MCP, connecting to Herdr, Codex app-server, and experimental ZCode/Amp connectors through a self-hosted relay without inbound ports.
    Apache 2.0
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

B3.4/5.0

Scored across 7 tools

Disambiguation3/5

The message-retrieval cluster (wait_for_message, read_inbox, ack_messages) has boundaries that are blurry, and the long cross-referential descriptions copy identical snapshot-review instructions into multiple tools, obscuring their distinct roles. send_message, check_snapshot, read_diff, and list_peers are clearly distinct, but the receive-side trio will cause occasional misselection.

Naming Consistency4/5

All tools follow a verb_noun snake_case pattern (send_message, wait_for_message, check_snapshot, list_peers, read_diff, ack_messages). The only minor deviation is read_inbox using a noun other than 'message' while its siblings use 'message', a small inconsistency but still readable and predictable.

Tool Count5/5

Seven tools is well-scoped for a peer messaging plus file-review protocol. Each tool maps to a needed operation (send, wait, read, ack, list peers, verify snapshot hash, inspect diff) with no obviously redundant entries.

Completeness4/5

The surface covers the messaging lifecycle (send/receive/acknowledge/peer discovery) and the review workflow (hash check, diff inspection). Coverage is solid; missing pieces like message history/search or an explicit file-send tool (currently delegated to the CLI snapshot command) are minor workarounds.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources