mcp-dispatch
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-dispatchdispatch message to bob: deployment complete"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-dispatch
Local inter-agent messaging for AI coding agents via MCP.
Multiple Claude Code sessions (or any MCP-compatible agents) running on the same machine can send messages to each other through a shared filesystem relay. No server process, no ports, no network — just directories and JSON files with atomic writes.
Features
Non-destructive messaging — Messages persist until explicitly acknowledged. No more lost messages from crashes or compaction.
Threading — Group messages into conversations with
thread_idandreply_to.Structured payloads — Attach machine-readable data alongside human-readable messages.
TTL & must_read — Time-sensitive messages auto-expire. Critical messages survive until acknowledged.
Delivery receipts —
peek()shows read/unread state of messages you've sent.Config-driven — TOML config for agent rosters, directories, and limits. Or go dynamic with no roster.
Zero infrastructure — Filesystem relay survives process crashes. No daemon to manage.
Related MCP server: mcp-terminal-share
Quick Start
1. Install
Requires Python 3.11+ and uv.
git clone https://github.com/sophia-labs/mcp-dispatch.git
cd mcp-dispatch
uv syncFor real-time stderr alerts when messages arrive (optional):
uv sync --extra watch2. Configure Claude Code
Add to your ~/.claude.json:
{
"mcpServers": {
"dispatch": {
"type": "stdio",
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-dispatch", "python", "server.py"],
"env": {
"MCP_DISPATCH_AGENT_ID": "alice"
}
}
}
}Each Claude Code window needs a unique MCP_DISPATCH_AGENT_ID.
3. Send messages
From any Claude Code session:
Agent alice: dispatch("Hey bob, I pushed the fix", target="bob")
Agent bob: peek() → sees alice's message
Agent bob: ack(["msg-abc12345"]) → message removedTools
Tool | Description |
| Send a message to one agent or all |
| Read messages and delivery receipts for sent messages |
| Acknowledge and delete processed messages |
| List connected agents |
dispatch
dispatch(
message="Deployed to staging",
target="all", # or a specific agent name
priority="normal", # "normal" or "urgent"
thread_id="deploy-123", # optional: group into conversation
reply_to="msg-abc", # optional: reference specific message
payload={"commit": "abc123", "env": "staging"}, # optional: structured data
ttl=3600, # optional: expire after 1 hour
must_read=True, # optional: survive TTL, require explicit ack
)peek
peek() # new (unread) messages only
peek(include_read=True) # all unacknowledged messages
peek(thread_id="deploy-123") # filter by threadack
ack(message_ids=["msg-abc", "msg-def"]) # delete specific messagesConfiguration
Create ~/.config/mcp-dispatch/config.toml:
# Agent roster (omit for dynamic registration — any name accepted)
agents = ["alice", "bob", "carol"]
# Message directory (default: ~/.config/mcp-dispatch/messages)
dispatch_dir = "~/.config/mcp-dispatch/messages"
# Maximum message size in bytes (default: 65536)
max_message_bytes = 65536
# Default TTL in seconds (0 = no expiry)
default_ttl = 0
# Custom MCP instructions template (optional)
# Placeholders: {agent_id}, {agent_list}
# instructions = "You are {agent_id}. Available agents: {agent_list}."Environment Variables
Variable | Description |
| Agent identity (required in dynamic mode) |
| Config file path (default: |
| Override dispatch directory from config |
Dynamic Mode
When no agents roster is configured, any agent name is accepted. Inbox directories are created on demand. This is more flexible but less safe (typos create phantom agents).
How It Works
Each agent gets an inbox directory (
{dispatch_dir}/{agent_name}/)Messages are JSON files written atomically (tmp + rename)
Presence is tracked via PID files in
{dispatch_dir}/.presence/Messages have states:
pending→read→ acknowledged (deleted)Piggyback delivery: pending messages are attached to every tool response
TTL cleanup runs lazily on read operations
Optional watchdog prints stderr alerts for the human operator
Message Format
{
"id": "msg-a1b2c3d4",
"from": "alice",
"to": "bob",
"timestamp": "2026-02-17T20:30:00Z",
"priority": "normal",
"content": "Deployed to staging",
"payload": {"commit": "abc123"},
"thread_id": "deploy-123",
"reply_to": null,
"ttl": 3600,
"must_read": false,
"state": "pending"
}License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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