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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sophia-labs/mcp-dispatch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server