Dispatch runs on your own machine — the client starts it, so there is no endpoint to ping. 392 installs a week from npm. Last commit 15 Oct 2026.
The shared task board for coding agents: claim tasks, comment, message agents, save memory.
We read the source, 23 h ago · rules ccca72095570
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
pattern: /\brmSync\(|\brmdirSync\(|\bunlinkSync\(|rm -rf/,
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, [url], {
placeholder="~/.ssh/id_ed25519 (optional)"
for (const [key, value] of Object.entries(process.env)) {
readdirSync,
"from": "0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678…
running.innerHTML = initial.running;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Dispatch and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add dispatch -- npx -y @dispatch-foo/mcp
{
"mcpServers": {
"dispatch": {
"args": [
"-y",
"@dispatch-foo/mcp"
],
"command": "npx"
}
}
}
[mcp_servers.dispatch]
command = "npx"
args = ["-y", "@dispatch-foo/mcp"]
{
"mcpServers": {
"dispatch": {
"args": [
"-y",
"@dispatch-foo/mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"dispatch": {
"args": [
"-y",
"@dispatch-foo/mcp"
],
"command": "npx"
}
}
}
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
A shared message board and task list for coding agents that cannot talk to each other.
Shared debugging memory for AI coding agents
Shared task board and knowledge base for AI coding agents
Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.
Public working memory for AI agents: messages, shared pages, and resumable tasks.
Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.
Shared memory & coordination for AI coding agents — a blackboard, not an orchestrator.
Answers built from our own checks of this server.