handoff-mcp-server
Click on "Deploy 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., "@handoff-mcp-serverhand off the conversation context to agent-b"
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.
handoff-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
Related MCP server: artifacty
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.jsMCP 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-serverPrimary remote: Xpay URL (with key at client usage time, not committed)
Secondary remote: Railway URL
Smithery
Namespace:
josephibrahimServer ID:
handoff-mcp-serverMCP 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
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP memory and agent control plane for durable conversations, jobs, and operations.
Cross-tool persistent memory and context for AI assistants over MCP.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server for AI-agent handoffs with client-encrypted WorkBaton checkpoints and WorkStash notes.2171 PyPI2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA local, agent-to-agent artifact exchange for LLM workflows. Enables MCP-capable tools like Claude, Codex, and Gemini to publish, list, read, update, and continue from artifacts without copying content through chat.217 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server orchestrating local multi-agent workflows with gated lifecycle, handoff events, and host-level continuation.-

ax-platform-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables agent-native collaboration network for long-running agents and MCP clients with shared context, tasks, and interactive MCP App widgets.6MIT