mcp-dispatch
Related Servers
Alternatives to mcp-dispatch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables real-time, file-based messaging between terminal AI agents (like Claude Code, Gemini CLI) allowing them to collaborate on tasks directly without a server or network, using JSON files and atomic rename for coordination.MIT
- AlicenseAqualityBmaintenanceEnables local AI coding agents to message each other on one machine using a durable SQLite mailbox and live-ask tools.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables multi-agent coordination for Claude Code and Claude.ai through file-based JSON communication, eliminating the human bottleneck of message relaying.3 npmMIT
- FlicenseCqualityDmaintenanceA lightweight messaging system that enables real-time communication between different AI agents through a shared, file-based message queue. It provides tools for sending, checking, and broadcasting messages to facilitate coordination across isolated project namespaces.81-
- AlicenseNot gradedqualityCmaintenanceFile-based MCP server for AI coding agents to coordinate via inbox messaging and human escalation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local agent-to-agent messaging between Claude Code sessions via file-based channels, with a registry, MCP tools and CLI for sending, reading, and tracking messages.2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct responsibility: dispatch sends, peek reads, ack deletes, and who lists agents. The only minor overlap is dispatch returning pending messages, but its primary purpose is unambiguous.
Tool names are consistently short, lowercase, and command-like, but they are not all verbs: dispatch, ack, and peek are actions while who is a query. This is a minor deviation from an otherwise coherent naming style.
Four tools is an ideal size for a messaging and dispatch server. Each tool covers a necessary operation without redundancy or bloat.
The message lifecycle is fully covered: create via dispatch, read via peek, remove via ack, plus agent discovery via who. Advanced features like reply_to, thread grouping, TTL, and payloads are supported through parameters, so there are no obvious gaps.