MCP.

RelayStation publishes a Model Context Protocol server card so any MCP-aware host — Claude Desktop, ChatGPT, Cursor, or a custom agent runtime — can discover the surface and call endpoints as tools.

Server card

The canonical server card lives at:

url

https://relaystation.ai/.well-known/mcp/server-card.json

Point your MCP host at that URL and it will auto-discover the tool list. No build step, no code to copy in. The card advertises:

Tools — relaystation_quote, relaystation_store, relaystation_handoff, relaystation_claim, and the Mailbox / Checkpoint families. Each tool has an inputSchema (JSON Schema) and an auth mode (none, x402, or jwt).
x402 discovery — the facilitator URL, network (base), and currency (USDC). MCP hosts that speak x402 can pay for calls directly.
Limits — max file size, min / max duration. Hosts can clamp agent inputs before emitting an x402 request.

Wiring examples

Claude Desktop

Add an entry to your claude_desktop_config.json:

json

{
  "mcpServers": {
    "relaystation": {
      "url": "https://relaystation.ai/.well-known/mcp/server-card.json"
    }
  }
}

Restart Claude Desktop. The tools surface automatically; the agent can call relaystation_quote with no auth, and relaystation_store with an attached x402 payment.

Custom host (agent runtime)

Fetch the server card, materialize each tool into your framework's tool schema, and route calls through your HTTP client. For x402 tools, plug an x402 client library that reads the required block from a 402 response and re-submits with a compliant X-Payment header.

Auth modes in the card

auth: "none": Free endpoints. relaystation_quote, relaystation_claim, and the public pricing fetches. No credential required.
auth: "x402": Priced endpoints callable with a per-request wallet payment. relaystation_store, relaystation_mailbox_create, relaystation_checkpoint_create. See x402 integration.
auth: "jwt": Owner-only operations against an existing lease. relaystation_handoff, the Mailbox poll/read endpoints, Checkpoint read/write. Your MCP host must present a Bearer token (API key or account JWT). See Auth.

What MCP doesn't cover

Dashboard-only paths (/v1/account/*, /v1/billing/*) are not exposed as MCP tools. They're for humans or server-side automation, not agent tool calls.
Multi-message Mailbox workflows beyond the headline "drop + pickup" are available in the card but live under extended tool names. Most MCP hosts will expose them only on explicit opt-in.

x402

→