ShipStatic

ShipStatic MCP

One URL. Your agent ships.

Deploy static websites, landing pages, and prototypes instantly. Free, no account needed.

Ask your agent to put your site online, and get back a real link you can share in seconds.

Try it in seconds, no account needed

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

ChatGPT

Add the ShipStatic plugin from its page in ChatGPT. There is nothing to paste.

Claude Desktop and claude.ai

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

Claude Code

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

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

{

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

VS Code

Install ShipStatic for VS Code. The server is built in, with no config at all.

Then just ask

"Publish this with ShipStatic."

Your agent publishes it, and you get back a link you can share right away, and a claim link. The site stays up for 3 days, and opening the claim link keeps it for good.

Want the site private? Say "publish this with ShipStatic's built-in password protection". Visitors have to type the password before they see anything, and saying "built-in" keeps your agent from writing a password page of its own.

Keep your sites with a free account

Everything above works with no account. A free account keeps your sites for good, gives you a ShipStatic domain like yourname.shipstatic.com, and shows you everything you've published in one place. A custom domain like www.example.com needs a paid plan.

Connect one when your client offers to sign you in, and the same URL answers with the rest. There's nothing to install and no key to paste: your client starts the sign-in itself.

Tools

All fifteen tools are on both doors. What changes is not which tools exist, but which ones answer: deployments_upload is the one that needs no account, and the other fourteen answer once you have connected one (hosted) or set SHIP_TOKEN (local).

Publishing, with no account

Deployments, with an account

Domains, with an account

Account, with an 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. A null cursor means you're 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 you get back the site the first try made, once it went live. A key works only within your account: an anonymous deploy ignores it, and a retry makes a new site.

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 removes it. That's useful for previews and quick experiments you'd otherwise have to remember to delete.

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

It needs an account (a connected account on the hosted endpoint, or SHIP_TOKEN locally): a deploy with no account 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 any domain: deploy without one when the site needs a domain.

Run it on your own machine

This package runs the same fifteen tools, reached the other way: as a local process instead of the hosted URL. Use it when your MCP client doesn't speak OAuth yet, or when you'd rather set a key once than sign in. To publish a folder from your own machine, use the ShipStatic CLI instead: it reads the files straight from disk.

It needs Node.js 20.19 or newer, and takes one setting, SHIP_TOKEN, whose value is your API key from my.shipstatic.com/api-key. Without it, the local server works like the hosted URL with no account connected.

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

Any other client takes the same command and setting in its mcp.json:

{

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

The MCP Registry lists ShipStatic as com.shipstatic/mcp, with the hosted URL.

Also available

License

MIT