xns-cloud/relayer-mcp

MCP server for XNS Relayer — S3-compatible decentralized object storage. Provides 15 tools that let an AI agent drive the complete Relayer setup and day-2 management conversationally over stdio transport.
**Pricing:** $6.00 per TB per month — one rate, protection included, $0 egress uncapped, 30-day minimum retention with no separate early-delete fee.
Requirements
On Ubuntu 24.04 or Debian 12, one command sets up everything:
The script installs Docker Engine and the compose plugin, adds you to the docker group, starts the Relayer in /opt/xns-relayer, and waits for the dashboard at http://localhost:8888. If Claude Code is present, it also installs Node.js 20 when Node is missing or older and registers this MCP. Log out and back in afterwards so the docker group applies. On macOS or Windows it installs nothing and points you to Docker Desktop.
Without the script, the MCP needs:
- **Node.js 20+** — see Installing Node.js 20 if your distro ships an older version.
- **Docker Engine** — on the same machine that runs the MCP. install_relayer refuses when the Docker daemon is on another machine (see Remote Docker hosts).
Installing Node.js 20
Ubuntu's default apt repository only ships Node 18, which is too old. Two ways to get Node 20:
**nvm** (recommended — no root required):
**NodeSource** (system-wide): follow .
If you start the MCP on an older Node, it exits immediately with this same guidance instead of a dependency stack trace.
Environment
The Relayer runs as a Docker container and persists its data in a Docker volume. If the MCP is running inside an ephemeral environment (a sandbox container, a CI runner, or a throwaway VM), any installation performed there will be lost when that environment exits. check_prerequisites detects this automatically and reports it as a warning with a concrete next step — it never blocks the flow.
**If your environment is ephemeral**, run the MCP on a persistent Docker host instead (install Node.js 20 there and point your MCP client at it). Alternatively, hand the install step to a human operator on the target machine and continue onboarding from check_relayer_health onwards.
Install
On Ubuntu 24.04 or Debian 12, one command installs the Relayer and registers this MCP when Claude Code is present:
To register the MCP by hand instead:
**Claude Code** (one command, if you registered nothing yet):
**Claude Desktop / any MCP client** — add to your claude_desktop_config.json (or equivalent):
**Cursor** — add to .cursor/mcp.json:
No separate install step required — npx fetches the package on demand.
Tools
| # | Tool | Purpose |
|---|------|---------|
| 1 | check_prerequisites | Verify Docker (local or remote), the compose plugin, Docker socket access (when it is denied, whether the docker group membership is missing or not yet live), ports (8888, 9000, 9443), an existing installation, free disk (10 GB on the Docker root and the install directory), and network connectivity. Each failure names the command that fixes it; ports held by a running xns-relayer pass. |
| 2 | start_registration | Get the browser sign-up URL for creating an XNS account — the agent never handles credentials. |
| 3 | check_email_verified | Poll email verification status (15s interval, 30-min timeout). |
| 4 | install_relayer | Fetch the canonical release channel bundle — relayer + Prometheus/Grafana monitoring stack (https://releases.scpri.me/relayer/release/docker-compose.yml and its .env, anonymous pull, no docker login) — add the ports to that .env, and start the containers. Falls back to a bundled service-parity copy if either fetch fails. A failure names its cause (port in use, image pull refused, Docker stopped, out of disk, Docker socket permission) and the fix. **Fresh installs only** — see Fresh installs vs. existing deployments. The user authors nothing; compose_url is an optional override for custom installs. |
| 5 | check_relayer_health | Poll UI, S3, HostIO, and the monitoring sidecars (10s interval, 300s timeout). A missing monitoring stack reports as degraded without blocking the flow. Targets the Docker host automatically. |