mcpField
S
ShipStatic · Static Hosting

ShipStatic · Static Hosting

Remote
shipstatic.comCloud & Infra6Updated 5d ago

About ShipStatic · Static Hosting

ShipStatic is an MCP server for publishing static sites, landing pages, and prototypes from AI agents. Anonymous deployments need no account, while a free account adds persistent hosting and custom-domain management.

Key features

  1. 01Publish files and receive a live URL
  2. 02Optional built-in password protection
  3. 03List and manage deployments
  4. 04Connect and verify custom domains
  5. 05Set deployment expiration times

Use cases

  1. 01Share a landing page produced by an agent
  2. 02Publish a prototype without signing up
  3. 03Manage deployments and custom domains
  4. 04Create expiring preview deployments

MCP support

Exposes deployment and domain-management tools to MCP clients through a hosted endpoint or local server. The anonymous upload tool works without an account; the other tools require a connected account or `SHIP_TOKEN`.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.shipstatic.com
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

15
ParameterTypeRequiredDescription
labelsarrayNoLabels for organizing deployments (e.g. ["production", "v1.2"]). Lowercase, 3-25 chars, allows . _ - separators.
pathstringYesAbsolute path to the build output directory to deploy (e.g. "/Users/me/project/dist")

Details

From the project README

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, lets you use your own domain, and shows you everything you've published in one place.

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
ToolDescription
deployments_uploadPublish files and get a live URL instantly, optionally protected by a password
Deployments, with an account
ToolDescription
deployments_listList all deployments with their URLs, status, labels, and password protection state. Pages with limit and cursor
deployments_getGet deployment details including URL, status, file count, size, labels, and password protection state
deployments_setUpdate the labels on a deployment for organization and filtering
deployments_deletePermanently delete a deployment and all its files
Domains, with an account
ToolDescription
domains_setConnect a custom domain to your site, switch deployments, or update labels
domains_listList all domains with their linked deployment and verification status. Pages with limit and cursor
domains_getGet domain details including linked deployment, verification status, and labels
domains_recordsGet the DNS records you need to configure at your DNS provider
domains_dnsThe DNS provider recorded for a domain, if known (e.g. Cloudflare, Namecheap)
domains_shareGet a shareable link so someone else can see the required DNS records
domains_validateCheck if a domain name is valid and available before connecting it
domains_verifyCheck if DNS is configured correctly after you set up the records
domains_deletePermanently disconnect and delete a custom domain
Account, with an account
ToolDescription
whoamiYour 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. 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

SurfaceReach it
CLI and SDKnpx @shipstatic/ship ./dist
VS CodeSearch "ShipStatic" in the Marketplace
PluginInstall it in Cursor, Claude Code, Codex or Gemini CLI
n8nSearch "ShipStatic" in n8n's node panel
GitHub Actionshipstatic/action@v3
Agent Skillnpx skills add shipstatic/plugin

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.