ShipStatic MCP

One URL. Your agent ships.

Give your AI a publish button for the internet: ask it to put your site online, and get back a real, shareable link in seconds. Landing pages, prototypes, portfolios — any static site.

One product, two doors in. Drop https://mcp.shipstatic.com into any MCP client — no install, no signup, no API key — and connect your account when your client asks: the full toolset, custom domains, sites that never expire. Install @shipstatic/mcp when your agent needs to deploy a folder on your own machine, when you'd rather configure a token once than sign in, or when your client doesn't speak OAuth yet — the same fifteen tools, reached the other way.

Hosted — nothing to install

Drop https://mcp.shipstatic.com into any MCP client. No install, no signup, no API key — your agent can publish a website in its next message.

https://mcp.shipstatic.com

Claude Code

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

Claude Desktop and claude.ai

Settings → Connectors → Add custom connector, paste https://mcp.shipstatic.com, save.

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

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

Then just ask

"Put my site online."

Your agent publishes the files and answers with two links:

• The live site — a real URL you can share right away.

• A claim link — the site stays live for 3 days; open the claim link to keep it forever. A free account is all it takes.

Want the site private? Ask for a password — visitors must enter it before they can see anything.

Then connect, if you want more

Everything above works with no account at all. Connect one when your client offers to sign you in, and the same URL answers with the rest: everything you've shipped, your own domains, and sites that stay up permanently. Nothing to install, no key to paste — your client starts the sign-in itself.

Related MCP server: deloc-mcp

Local — the same tools, from your own machine

Install this package when your agent needs to deploy a folder on your own machine — the hosted endpoint takes files inline, so it has no path to read from — when you'd rather configure a token once than sign in, or when your MCP client doesn't speak OAuth yet.

The config asks for one thing: SHIP_TOKEN. Its value is your API key — one credential, two names. The console mints it as an API key (it looks like ship-...), and the setting that carries it is called the token. Get yours free at my.shipstatic.com/api-key, paste it where the snippets below show ship-..., and every site you publish lands in your account, never expires, and gets bigger limits.

The key is optional: leave it out and the local server behaves like the hosted endpoint with no account connected (public sites, claim links, live for 3 days).

The server runs with npx, which ships with Node.js (20.19 or newer).

Claude Code

claude mcp add shipstatic -e SHIP_TOKEN=ship-... -- npx -y @shipstatic/mcp

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "shipstatic": {
      "command": "npx",
      "args": ["-y", "@shipstatic/mcp"],
      "env": { "SHIP_TOKEN": "ship-..." }
    }
  }
}

Antigravity

Add to ~/.gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "shipstatic": {
      "command": "npx",
      "args": ["-y", "@shipstatic/mcp"],
      "env": { "SHIP_TOKEN": "ship-..." }
    }
  }
}

Windsurf, Zed, and other MCP clients

Same config shape — npx -y @shipstatic/mcp, with SHIP_TOKEN in env. Works with any MCP-compatible client.

VS Code

Prefer an editor extension? ShipStatic for VS Code has this server built in — no config at all.

Tools

All fifteen tools are on both doors. deployments_upload is the one that needs no account; connect on the hosted endpoint or set SHIP_TOKEN locally and the other fourteen answer too.

Deployments

Domains

Account

Paging long lists

deployments_list and domains_list accept limit and cursor. Each response carries a cursor — pass it back to fetch the next page; null means you are on the last one.

Retrying a deploy safely

deployments_upload accepts an idempotencyKey. If a deploy times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying without a key creates a second site. Send the same key on the retry and the original deployment is returned instead.

Key the attempt, not the try — a run id, a commit sha, or a uuid generated before the first call. A key that changes on every retry does nothing.

Deployments that clean themselves up

deployments_upload accepts a ttl in seconds. The deployment expires when the time is up and the platform reclaims it — handy for previews and throwaway iterations you would otherwise have to remember to delete.

{ "path": "/path/to/dist", "ttl": 3600 }

It needs SHIP_TOKEN (your API key): a keyless deploy already expires on the platform's schedule, so a ttl on one is refused rather than ignored. A deployment carrying a ttl cannot be linked to a custom domain — deploy without one when the site needs a domain.

Registry

Published to the MCP Registry as com.shipstatic/mcp. Registry-aware clients see both the hosted endpoint and the local install and pick whichever fits their environment.

License

MIT