About handoff-mcp-server
handoff-mcp-server provides durable handoffs and a shared scratchpad for multi-agent workflows. It is an HTTP-based MCP server with configurable API-key authentication for tool calls.
Key features
- 01Durable agent-to-agent handoffs
- 02Shared workflow scratchpad
- 03HTTP transport for MCP
- 04Configurable tool-call authentication
Use cases
- 01Pass work between agents
- 02Share notes during multi-agent workflows
MCP support
It exposes handoff and scratchpad capabilities through an HTTP MCP endpoint at `/mcp`. Discovery methods may be public, while tool calls require valid authentication when an API key is configured.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://handoff-mcp-server-production.mcp.xpay.sh/mcpclaude mcp add --transport http josephibra-handoff https://handoff-mcp-server-production.mcp.xpay.sh/mcp{"mcpServers":{"josephibra-handoff":{"type":"http","url":"https://handoff-mcp-server-production.mcp.xpay.sh/mcp"}}}Open in Cursor{"servers":{"josephibra-handoff":{"type":"http","url":"https://handoff-mcp-server-production.mcp.xpay.sh/mcp"}}}Open in VS Code{"mcpServers":{"josephibra-handoff":{"type":"http","url":"https://handoff-mcp-server-production.mcp.xpay.sh/mcp"}}}{"mcpServers":{"josephibra-handoff":{"serverUrl":"https://handoff-mcp-server-production.mcp.xpay.sh/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://handoff-mcp-server-production.mcp.xpay.sh/mcphttps://handoff-mcp-server-production.up.railway.app/mcpTools
Details
From the project READMEhandoff-mcp-server
Durable handoffs and shared scratchpad for multi-agent workflows over MCP (HTTP transport).
Endpoints
GET /basic service infoGET /healthhealth and storage statsPOST /mcpJSON-RPC MCP endpointGET /robots.txtdiscovery fileGET /llms.txtdiscovery fileGET /sitemap.xmldiscovery file
Environment Variables
PORTdefault3000DATA_DIRdefault/dataMCP_API_KEYrequired in production (NODE_ENV=production)PUBLIC_MCP_DISCOVERYdefaulttruePUBLIC_BASE_URLoptional, used for absolute links in discovery files
Local Run
npm ci
npm run build
MCP_API_KEY=test-secret node dist/index.js
MCP Auth Behavior
- Discovery methods (
initialize,tools/list,resources/list,prompts/list,ping) can be public whenPUBLIC_MCP_DISCOVERY=true. tools/callrequires valid upstream auth whenMCP_API_KEYis set:Authorization: Bearer <MCP_API_KEY>orx-api-key: <MCP_API_KEY>
Xpay + Railway Configuration (Required)
- Railway variables:
MCP_API_KEY=<your-strong-key>PUBLIC_MCP_DISCOVERY=truePUBLIC_BASE_URL=https://handoff-mcp-server-production.up.railway.app
- Xpay MCP URL:
- Use
https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_... - Without
?key=..., Xpay returns auth required and requests will not forward.
- Client calls through Xpay:
- Keep the Xpay key in URL.
- Also send upstream auth header for
tools/call(x-api-keyor Bearer token matchingMCP_API_KEY).
Publishing
MCP Registry
- Server name:
io.github.josephibra/handoff-mcp-server - Primary remote: Xpay URL (with key at client usage time, not committed)
- Secondary remote: Railway URL
Smithery
- Namespace:
josephibrahim - Server ID:
handoff-mcp-server - MCP Server URL:
https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...
Agentverse
- Create a new agent and attach MCP server:
- URL:
https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_... - Headers:
x-api-key: <MCP_API_KEY>for tool execution paths
- URL:
Recommended Extra Discovery Listings
- PulseMCP directory
- mcp.so
- OpenTools catalog
- MCPmarket / mcpservers.org
Use the same canonical MCP URL and matching auth notes everywhere to avoid inconsistent behavior.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.