io.github.josephibra/handoff-mcp-server

Official registry AI and agents

Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http handoff-mcp-server 'https://handoff-mcp-server-production.mcp.xpay.sh/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "handoff-mcp-server": {
            "type": "http",
            "url": "https://handoff-mcp-server-production.mcp.xpay.sh/mcp"
        }
    }
}
Remote (streamable-http)
Claude Code
claude mcp add --transport http handoff-mcp-server 'https://handoff-mcp-server-production.up.railway.app/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "handoff-mcp-server": {
            "type": "http",
            "url": "https://handoff-mcp-server-production.up.railway.app/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. handoff-mcp-server
  2. Endpoints
  3. Environment Variables
  4. Local Run
  5. MCP Auth Behavior
  6. Xpay + Railway Configuration (Required)
  7. Publishing
  8. Recommended Extra Discovery Listings

handoff-mcp-server

Durable handoffs and shared scratchpad for multi-agent workflows over MCP (HTTP transport).

Endpoints

  • GET / basic service info
  • GET /health health and storage stats
  • POST /mcp JSON-RPC MCP endpoint
  • GET /robots.txt discovery file
  • GET /llms.txt discovery file
  • GET /sitemap.xml discovery file

Environment Variables

  • PORT default 3000
  • DATA_DIR default /data
  • MCP_API_KEY required in production (NODE_ENV=production)
  • PUBLIC_MCP_DISCOVERY default true
  • PUBLIC_BASE_URL optional, 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 when PUBLIC_MCP_DISCOVERY=true.
  • tools/call requires valid upstream auth when MCP_API_KEY is set:
    • Authorization: Bearer <MCP_API_KEY> or
    • x-api-key: <MCP_API_KEY>

Xpay + Railway Configuration (Required)

  1. Railway variables:
  • MCP_API_KEY=<your-strong-key>
  • PUBLIC_MCP_DISCOVERY=true
  • PUBLIC_BASE_URL=https://handoff-mcp-server-production.up.railway.app
  1. 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.
  1. Client calls through Xpay:
  • Keep the Xpay key in URL.
  • Also send upstream auth header for tools/call (x-api-key or Bearer token matching MCP_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
  • PulseMCP directory
  • mcp.so
  • OpenTools catalog
  • MCPmarket / mcpservers.org

Use the same canonical MCP URL and matching auth notes everywhere to avoid inconsistent behavior.

Frequently asked questions

What is io.github.josephibra/handoff-mcp-server?

Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.

How do I install io.github.josephibra/handoff-mcp-server?

It runs as a remote server. In Claude Code: claude mcp add --transport http handoff-mcp-server 'https://handoff-mcp-server-production.mcp.xpay.sh/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.josephibra/handoff-mcp-server need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.josephibra/handoff-mcp-server open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.josephibra/handoff-mcp-server?

It is published by josephibra. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.