Agent Handoff MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Oct 2026.
Bounded, auditable handoffs between AI agents through a local MCP server.
What the code does
We read the source, 3 h ago · rules 995398eba69f
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(process.execPath, args, { cwd: root, env, timeout, windowsHide: true });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- /var/run/docker.sock:/var/run/docker.sock:ro
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
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 agent-handoff-mcp -e 'HANDOFF_AGENT_ID=<HANDOFF_AGENT_ID>' -e 'HANDOFF_MCP_REGISTRY=<HANDOFF_MCP_REGISTRY>' -e 'HANDOFF_MCP_DB=<HANDOFF_MCP_DB>' -- npx -y @sarutobi-sasuke/agent-handoff-mcp{
"mcpServers": {
"agent-handoff-mcp": {
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/agent-handoff-mcp"
],
"env": {
"HANDOFF_AGENT_ID": "<HANDOFF_AGENT_ID>",
"HANDOFF_MCP_DB": "<HANDOFF_MCP_DB>",
"HANDOFF_MCP_REGISTRY": "<HANDOFF_MCP_REGISTRY>"
}
}
}
}[mcp_servers.agent-handoff-mcp]
command = "npx"
args = ["-y", "@sarutobi-sasuke/agent-handoff-mcp"]
env = { HANDOFF_AGENT_ID = "<HANDOFF_AGENT_ID>", HANDOFF_MCP_REGISTRY = "<HANDOFF_MCP_REGISTRY>", HANDOFF_MCP_DB = "<HANDOFF_MCP_DB>" }{
"mcpServers": {
"agent-handoff-mcp": {
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/agent-handoff-mcp"
],
"env": {
"HANDOFF_AGENT_ID": "<HANDOFF_AGENT_ID>",
"HANDOFF_MCP_DB": "<HANDOFF_MCP_DB>",
"HANDOFF_MCP_REGISTRY": "<HANDOFF_MCP_REGISTRY>"
}
}
}
}{
"servers": {
"agent-handoff-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sarutobi-sasuke/agent-handoff-mcp"
],
"env": {
"HANDOFF_AGENT_ID": "<HANDOFF_AGENT_ID>",
"HANDOFF_MCP_DB": "<HANDOFF_MCP_DB>",
"HANDOFF_MCP_REGISTRY": "<HANDOFF_MCP_REGISTRY>"
}
}
}
}Put your own values in place of
<HANDOFF_AGENT_ID> (Existing enabled identity in the operator-provisioned registry), <HANDOFF_MCP_REGISTRY> (Absolute path to the operator-provisioned agent registry YAML), <HANDOFF_MCP_DB> (Absolute path to the local handoff SQLite database).
The author’s registry entry marks them as required.
Alternatives to Agent Handoff MCP
same job, measured the same wayLocal QMD search and bounded index maintenance through a Streamable HTTP MCP server.
Find and book verified local home service professionals through AI agents.
Connect AI agents to Flato's editable canvas runtime through a hosted MCP server.
Control and verify a live Unity Editor through a local, low-token MCP server.
Find and book verified local home service professionals through AI agents.
Manage Authentik through AI assistants
MCP server connecting AI assistants to Autodesk Revit through a local bridge.
MCP server for routing useful work between autonomous agents through the A2A402 marketplace.
Agent Handoff MCP — questions
Answers built from our own checks of this server.