shipstatic/mcp

**One URL. Your agent ships.**
> ⚡ **You probably don't need to install this.** The same server is hosted at **https://mcp.shipstatic.com** — drop that URL into any MCP client and your agent can publish a website in its next message. No install, no Node.js, no signup, no API key.
>
> **This package is the local alternative.** Install it 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. Local setup ↓
Deploy static websites, landing pages, and prototypes instantly from AI agents. Ask yours to put your site online and get back a real, shareable link in seconds.
Hosted: start here
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.
Claude Code
Claude Desktop and claude.ai
**Settings → Connectors → Add custom connector**, paste https://mcp.shipstatic.com, save.
Cursor, Antigravity, Windsurf, n8n, Zed — anywhere with mcp.json
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 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? Say "publish this with ShipStatic's built-in password protection". Visitors must enter the password before they can see anything, and saying "built-in" keeps your agent from writing a password page of its own.
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.
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 starts with 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-your-api-key, and every site you publish lands in your account and never expires, with a rate limit of your own instead of the shared anonymous pools.
The key is optional: leave it out and the local server behaves exactly 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
Cursor
Add to ~/.cursor/mcp.json:
Antigravity
Add to ~/.gemini/antigravity/mcp_config.json:
Windsurf, Zed, and other MCP clients
Same config shape — npx -y @shipstatic/mcp, with SHIP_TOKEN in env. Works with any MCP-compatible client.
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).