mcp-dispatch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DISPATCH_DIR | No | Override dispatch directory from config | |
| MCP_DISPATCH_CONFIG | No | Config file path (default: ~/.config/mcp-dispatch/config.toml) | ~/.config/mcp-dispatch/config.toml |
| MCP_DISPATCH_AGENT_ID | Yes | Agent identity (required in dynamic mode) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dispatchA | Send a message to another agent or all agents. Use priority='urgent' for time-sensitive messages. Optional: thread_id groups messages into conversations, reply_to references a specific message, payload carries structured data (dict), ttl sets expiry in seconds, must_read=true prevents auto-expiry. Returns confirmation plus any pending messages for you. |
| peekA | Read incoming messages without deleting them. By default returns only NEW (unread) messages with full bodies. Set include_read=true to see ALL unacknowledged messages. Filter by thread_id to see a specific conversation. Use ack() to acknowledge messages when you're done with them. Also returns delivery receipts for your recently sent messages. Modes:
since: ISO8601 timestamp filter — only return messages with timestamp >= since. |
| ackA | Acknowledge and delete messages by their IDs. This is the only way to permanently remove messages from your inbox (besides TTL expiry). Pass a list of message IDs to acknowledge. |
| whoA | List all currently connected agents and their status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.