The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Handoff MCP Server listing page.
Durable handoffs and shared scratchpad for multi-agent workflows over MCP (HTTP transport).
GET / basic service infoGET /health health and storage statsPOST /mcp JSON-RPC MCP endpointGET /robots.txt discovery fileGET /llms.txt discovery fileGET /sitemap.xml discovery filePORT default 3000DATA_DIR default /dataMCP_API_KEY required in production (NODE_ENV=production)PUBLIC_MCP_DISCOVERY default truePUBLIC_BASE_URL optional, used for absolute links in discovery filesinitialize, tools/list, resources/list, prompts/list, ping) can be public when PUBLIC_MCP_DISCOVERY=true.tools/call requires valid upstream auth when MCP_API_KEY is set:
Authorization: Bearer <MCP_API_KEY> orx-api-key: <MCP_API_KEY>MCP_API_KEY=<your-strong-key>PUBLIC_MCP_DISCOVERY=truePUBLIC_BASE_URL=https://handoff-mcp-server-production.up.railway.apphttps://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...?key=..., Xpay returns auth required and requests will not forward.tools/call (x-api-key or Bearer token matching MCP_API_KEY).io.github.josephibra/handoff-mcp-serverjosephibrahimhandoff-mcp-serverhttps://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...x-api-key: <MCP_API_KEY> for tool execution pathsUse the same canonical MCP URL and matching auth notes everywhere to avoid inconsistent behavior.