deployments_delete
Permanently delete a deployment and its files. You MUST confirm with the user before calling this tool, referencing the deployment.
LABSCO SUMMARY
A publish button that works before you have an account.
The first deploy answers with two links: the live site, and a claim link that converts 3 days of hosting into permanent hosting for free. The local package exists for the one thing the hosted endpoint cannot do — read a build directory off your own disk — and everything past the first deploy, listing, domains, permanence, is what an account buys.
What it is
A static-site publishing server with two doors: a hosted endpoint at https://mcp.shipstatic.com that needs no install and no signup, and this npm package for when the agent has to deploy a folder sitting on your own machine. The same fifteen tools are on both.
What you get
- deployments_upload publishes the directory at path and returns the live URL, the file count and the size — with no account, the reply also carries a claim URL and the site expires in 3 days.
- A password on the same call puts an unlock prompt in front of the site, including on any custom domain pointing at it.
- An idempotencyKey makes a retried deploy replay the original rather than create a second site.
- A ttl in seconds lets a preview deployment expire on its own instead of waiting to be remembered and deleted.
- deployments_list, deployments_get and deployments_set read back URLs, status, size, labels and password state, and replace the labels on one.
- deployments_delete removes a deployment and its files permanently, after confirming with you by name.
- domains_validate says whether a name is valid and available and returns its normalized form; domains_set reserves it, links it to a deployment, or switches which deployment it points at.
- domains_records returns the DNS records to configure, domains_dns names the provider hosting that domain — Cloudflare, Namecheap — and domains_verify triggers verification once the records are live.
- domains_share hands out a link to the required DNS records that works without an API key.
- whoami reports the account behind the connection: email, plan and usage.
Requirements
Nothing for a first deploy — deployments_upload states that it needs no account and no API key. The other fourteen tools answer once an account is connected on the hosted endpoint, or once SHIP_TOKEN carries your API key locally; the console mints it starting with ship-, free at my.shipstatic.com/api-key. The local package runs under npx, which ships with Node.js 20.19 or newer.
Setup effort
One command — claude mcp add --transport http shipstatic https://mcp.shipstatic.com
USE CASES
01
Getting a prototype in front of someone right now
Deploy the site and share the URL that comes back — no account needed, and the site holds for 3 days unless you open the claim link. The hosted endpoint takes the files inline; to deploy a build folder straight off your disk, run the local package.
02
Sharing a draft that should not be public
Pass a password on the deploy and visitors have to enter it before they see anything — on the deployment's own URL and on any custom domain in front of it.
03
Putting a real domain in front of a site
Check the name is available, link it to the deployment, read out the DNS records, then verify once they have propagated.
04
Handing the DNS step to whoever owns the zone
Look up which provider hosts the domain, then send a share link that shows the required records without giving anyone an API key.
05
Retrying a deploy that timed out
A timeout cannot tell you whether the deploy landed. Send the same idempotencyKey — a run id or a commit sha minted before the first attempt — and the original deployment is replayed instead of a second one appearing.
06
Clearing out preview sites you would otherwise forget
Give throwaway deploys a ttl so the platform reclaims them, and go through what is left to relabel or delete it.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
deployments_get
Get deployment details including URL, status, file count, size, labels, and password protection state.
deployments_list
List all deployments with their URLs, status, labels, and password protection state. The response's cursor is null on the last page; pass it back as cursor to fetch the next.
deployments_set
Update deployment labels. Replaces all existing labels.
deployments_upload
Deploy a static site instantly — free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response includes a claim URL (site expires in 3 days) — always show both the deployment URL and claim URL to the user. To make the site private, pass password; always show the password to the user if you set one.
domains_delete
Permanently delete a domain. You MUST confirm with the user before calling this tool, referencing the domain name.
domains_dns
Look up the DNS provider for a domain (e.g. Cloudflare, Namecheap). Helps the user know where to configure their DNS records.
domains_get
Get domain details including URL, linked deployment, verification status, and labels.
domains_list
List all domains with their URLs, linked deployment, and verification status. The response's cursor is null on the last page; pass it back as cursor to fetch the next.
domains_records
Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.
domains_set
Create or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. After creating, call domains_records and show the DNS records to the user.
domains_share
Get a shareable DNS setup hash for a domain. The hash can be shared with the user so they can view the required DNS records without needing an API key.
domains_validate
Check if a domain name is valid and available before creating it. Returns the normalized form and availability.
domains_verify
Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Verification is asynchronous — the domain status updates once DNS propagates.
whoami
Show authenticated account details including email, plan, and usage.
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. Only deployments_upload works without an account; the other fourteen need a connected account (hosted) or SHIP_TOKEN (local). Only the local package can deploy a folder by path.
Requires
A client that can reach a remote MCP server over HTTP
Optional
SHIP_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code — remote
TERMINAL
claude mcp add --transport http shipstatic https://mcp.shipstatic.comHosted endpoint
ENDPOINT URL
https://mcp.shipstatic.comAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Code — local
CLAUDE CODE — LOCAL · TERMINAL
claude mcp add shipstatic -e SHIP_TOKEN=<YOUR_SHIP_TOKEN> -- npx -y @shipstatic/mcpClaude Desktop, Claude.ai
Settings → Connectors → Add custom connector, paste https://mcp.shipstatic.com
Cursor, Antigravity
JSON
{
"mcpServers": {
"shipstatic": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
],
"env": {
"SHIP_TOKEN": "<YOUR_SHIP_TOKEN>"
}
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"shipstatic": {
"serverUrl": "https://mcp.shipstatic.com"
}
}
}Other MCP clients
OTHER MCP CLIENTS · JSON
{
"mcpServers": {
"shipstatic": {
"url": "https://mcp.shipstatic.com"
}
}
}VS Code
Install the ShipStatic VS Code extension — the server is built in, with no config at all
