hoptell
Related Servers
Alternatives to hoptell
- AlicenseNot gradedqualityDmaintenanceMCP server for async messaging between AI coding agents, enabling cross-harness and cross-machine communication with Slack-like semantics and mail-shaped delivery.2MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP 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.11,423 npmMIT
- AlicenseAqualityAmaintenanceSelf-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.9MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.MIT
- AlicenseAqualityDmaintenanceMCP 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.837 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.23 npm20MIT
- AlicenseAqualityAmaintenanceLocal agent-to-agent messaging and coordination for coding sessions on one machine, through MCP and a CLI. Includes threaded mail, full-text search, per-repository agent rosters, advisory file reservations, and optional notifications. Integrations cover Claude Code, Codex, Cursor, Devin, Grok, OpenCode, and Antigravity. Standalone agents and T3 Code sessions can share the same local server.2221MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list peers, retrieve queued messages, send messages, and block for incoming messages. The potential overlap between read_inbox and wait_for_message is well-resolved by descriptions specifying non-blocking retrieval versus blocking wait.
All tools follow a consistent snake_case verb-first pattern (list_peers, read_inbox, send_message, wait_for_message). The slight variation in wait_for_message with a preposition is common and does not break predictability.
Four tools is well-scoped for a peer messaging server, covering discovery, sending, queued receiving, and blocking receiving without redundancy or bloat. Every tool earns its place.
The surface covers the full messaging lifecycle: peer discovery, send (including broadcast to roles/all), and two complementary receive modes (non-blocking queued and blocking wait). No obvious gaps for the stated purpose.