Add one MCP server to Claude and say “set up XNS storage.” It stands up a private, S3-compatible Relayer on your own Docker host — register, deploy, claim, verify — conversationally. You click one email link and one sign-in; the agent does the rest.
npx
No install step — runs on demand
15 tools
Full setup, start to finish
Docker
Self-hosted on your own host
$0 egress
Once your Relayer is running
One command
Point Claude Code — or any MCP client — at the XNS installer. There is no separate download: npx fetches the published package on demand.
claude mcp add relayer -- npx @xns-cloud/relayer-mcp@latest
{
"mcpServers": {
"relayer": {
"command": "npx",
"args": ["@xns-cloud/relayer-mcp@latest"]
}
}
}
Then just tell your agent: “Set up XNS storage.” It takes over from there.
What the agent does
The MCP drives a complete Relayer setup over stdio. Your only actions are clicking one email link, completing one browser sign-in, and confirming one claim.
Self-hosted: the MCP installs Relayer on a machine you control. Fresh installs only — an existing Relayer container is detected first, never clobbered.Step What happens 1. Check prerequisites Verifies Docker, free ports (8888 / 9000), disk, and connectivity. 2. Register your account Creates your XNS account; you click one email verification link. 3. Install & start Relayer Pulls the released compose bundle (Relayer + monitoring) and brings the containers up on your Docker host. You author nothing. 4. Wait for health Polls until the UI and S3 gateway are up. 5. Claim the node You confirm one browser sign-in to bind the node to your account. 6. Compose host preferences Sets data / parity host selection (your VPD) over OIDC. 7. Verify storage Runs a real S3 round-trip — create bucket, put object, get object. 8. Provision CLI credentials Writes ~/.xns/credentials so the xns CLI works immediately.
What you need: Node.js 20+ and Docker Engine — on the same machine, or a remote host reached through a Docker context. Nothing else.
After setup
Day-to-day storage operations run through the xns CLI — ls, cp, sync, rm, presign — fast, scriptable, and easy on an agent’s context. Or point any S3 SDK at your endpoint; XNS speaks standard S3.
xns cp ./data s3://my-bucket/ --recursive
aws s3 --endpoint-url https://relayer.example.com ls
Questions an agent asks
Add the XNS installer MCP, then ask your agent to set it up. In Claude Code: It is Node.js 20 or newer and Docker Engine — local, or a remote host via a Docker context. The package runs through The agent does nearly all of it. You click one email verification link, complete one browser sign-in, and confirm one claim. You never author a compose file or config. A self-hosted XNS Relayer — the S3 gateway plus a Prometheus/Grafana monitoring stack — from the released Docker compose bundle, on a machine you control. It performs fresh installs only and detects any existing Relayer before touching anything. Use the How do I set up XNS storage with Claude or an AI agent?
claude mcp add relayer -- npx @xns-cloud/relayer-mcp@latest. Then say “set up XNS storage” and the agent registers your account, installs a Relayer on your Docker host, claims it, and verifies S3.What is the XNS MCP server?
@xns-cloud/relayer-mcp, a published npm package that exposes 15 tools letting an AI agent stand up and onboard an XNS Relayer (an S3-compatible storage gateway) conversationally over stdio. It is the install path; the xns CLI handles day-to-day storage ops.What do I need to run it?
npx, so there is no separate install step.Does the agent do everything, or do I have to act?
What does it actually install?
How do I run storage operations after setup?
xns CLI (ls, cp, sync, rm, presign), which the MCP configures for you, or point any standard S3 SDK (boto3, aws-cli, rclone, restic) at your endpoint.
Add one MCP server, say the words, and watch a private S3 datacenter assemble itself.