⚡ 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.
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.
Deploy static websites, landing pages, and prototypes instantly. Free, no account needed.
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.
https://mcp.shipstatic.com
Claude Code
claude mcp add --transport http shipstatic https://mcp.shipstatic.com
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
claude mcp add shipstatic -e SHIP_TOKEN=ship-your-api-key -- npx -y @shipstatic/mcp
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).
Publishing — no account needed
Tool
Description
deployments_upload
Publish files and get a live URL instantly, optionally protected by a password
Deployments — with an account
Tool
Description
deployments_list
List all deployments with their URLs, status, labels, and password protection state. Pages with limit and cursor
deployments_get
Get deployment details including URL, status, file count, size, labels, and password protection state
deployments_set
Update the labels on a deployment for organization and filtering
deployments_delete
Permanently delete a deployment and all its files
Domains — with an account
Tool
Description
domains_set
Connect a custom domain to your site, switch deployments, or update labels
domains_list
List all domains with their linked deployment and verification status. Pages with limit and cursor
domains_get
Get domain details including linked deployment, verification status, and labels
domains_records
Get the DNS records you need to configure at your DNS provider
domains_dns
The DNS provider recorded for a domain, if known (e.g. Cloudflare, Namecheap)
domains_share
Get a shareable link so someone else can see the required DNS records
domains_validate
Check if a domain name is valid and available before connecting it
domains_verify
Check if DNS is configured correctly after you set up the records
domains_delete
Permanently disconnect and delete a custom domain
Account — with an account
Tool
Description
whoami
Your email and name, and the account's plan, usage and caps
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 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 reclaims it — handy for previews and throwaway iterations you would otherwise have to remember to delete.
{ "path": "/path/to/dist", "ttl": 3600 }
It needs an account — SHIP_TOKEN here, a connected account on the hosted endpoint: 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.
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.
