Your agent ships.

Nothing was installed and nothing was configured before that. An agent with a shell can do this today; an MCP client calls deployments_upload and gets the same two URLs back.

What you can ask

Connect an account, which your client offers the first time you ask for something that needs one, and your agent can also list deployments, link custom domains, switch live versions, and look up DNS records: "Connect www.example.com to the latest deployment" or "Show me the DNS records I need to set up."

How it works

Run one command

If your agent can run a shell command, there is nothing to set up on either side. npx fetches the CLI on first use and publishes whatever folder you point it at.

npx -y @shipstatic/ship ./dist

Four things worth telling your agent:

• Keep the -y. Without it npx stops at an install prompt, and a non-interactive runtime waits there forever.
• Point it at built output, so ./dist, ./build or ./out, never a project root. Build first if the project needs it.
• Add --json to read the result. It prints machine-readable output on success and on failure; branch on error and status, never on the message text.
• Always show both URLs. The live one, and the claim link. That link is the only thing that keeps the site past 3 days.

CLI docs · Teach it the whole workflow with the skill

Or add one URL

If your agent has no shell, or you would rather it had native tools than a command to remember: same URL, every client. Drop it into your MCP config and your agent picks it up on the next session.

Claude Code

claude mcp add --transport http shipstatic https://mcp.shipstatic.com

Cursor, Antigravity, Windsurf, n8n, Zed, anywhere with mcp.json

{
  "mcpServers": {
    "shipstatic": {
      "url": "https://mcp.shipstatic.com"
    }
  }
}

Claude Desktop, Claude.ai web: add a custom connector pointing at https://mcp.shipstatic.com.

VS Code: install the ShipStatic extension. The MCP server is built in.

Publishing needs no account

Connecting is optional and reversible. You can disconnect from the same place in your client at any time, and publishing without an account keeps working exactly as it did.

Prefer to run it yourself?

The same fifteen tools also run as a local process. Reach for it when your agent needs to publish a folder on your own machine, since the URL above takes files inline and has no path to read from. It also helps when you would rather configure a free API key once than sign in, or when your client does not speak OAuth yet.

claude mcp add shipstatic -e SHIP_TOKEN=ship-your-api-key -- npx -y @shipstatic/mcp

SHIP_TOKEN takes your API key. It is one credential with two names: the console mints it as an API key, and every setting that carries it is called the token.

MCP docs · npm · GitHub · MCP Registry

More ways in

Every one of these publishes with no account and returns the same live URL and claim link. Choose by what your agent can already do.

curl --create-dirs -so .claude/skills/ship/SKILL.md https://www.shipstatic.com/SKILL.md

n8n-nodes-shipstatic

Machine-readable documentation