Shipstatic MCP

What shipstatic/mcp MCP server does

shipstatic/mcp exposes ShipStatic's static hosting workflow through MCP. Agents can upload a folder of site files and receive a live URL, file count, and total size. Anonymous uploads can also return a one-time claim URL; unclaimed sites expire after three days. Uploads may include password protection.

With an account connected, the toolset also covers deployment and domain administration. Agents can list, inspect, label, and permanently delete deployments, then create or update custom-domain associations. Domain tools report verification state, provide DNS records, identify a recorded DNS provider, generate a shareable DNS setup link, validate availability, trigger verification, and remove domains. whoami reports the account identity, plan, usage, and caps.

How it works

The hosted MCP endpoint is available at https://mcp.shipstatic.com. An MCP client connects to that URL and can invoke the same fifteen tools without installing the package. Anonymous access is centered on deployments_upload; the remaining account-oriented tools respond after a hosted account sign-in or when a token is configured locally.

The local package runs as an MCP process and reaches the same tool set through stdio. It is useful for clients that do not support the hosted sign-in flow or for setups that prefer a token in client configuration. It does not read a local folder for upload automatically; the ShipStatic CLI is the separate surface for publishing files directly from disk.

Deployment and domain lists support limit and cursor. Pass the returned cursor to request the next page; a null cursor marks the final page. Uploads can use an idempotency key for account-based retries, so a timed-out request can be safely repeated without creating a duplicate deployment. The same key must identify the overall attempt and is ignored for anonymous uploads.

Setup and configuration

For the hosted service, add https://mcp.shipstatic.com as a custom MCP connector or server URL. Claude Desktop and claude.ai use the custom connector settings; Claude Code can be configured with its HTTP transport; clients using mcp.json can define the URL directly.

For local use, install and launch the package with npx -y @shipstatic/mcp. Node.js 20.19 or newer is required. Set SHIP_TOKEN to an API key from ShipStatic when account-backed local access is needed:

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

The hosted endpoint can also be used without an account. A connected account keeps sites permanently and enables custom domains; anonymous sites follow the platform's expiration behavior until claimed.

Tools and capabilities

• Upload static files, optionally with a password, time-to-live, and idempotency key.
• List, inspect, label, and delete deployments.
• Create, link, relink, label, verify, and delete custom domains.
• Retrieve DNS records, DNS-provider information, and shareable DNS setup links.
• Validate domain names and check asynchronous verification results.
• Inspect account identity, plan, usage, and limits.
• Page through deployment and domain lists with cursors.

Limitations and notes

A deployment with a ttl requires an account and cannot be linked to a domain. Anonymous deployments already use the platform's expiration schedule, so a TTL is refused for them. A verified domain serves no site until it is linked to a deployment. DNS verification is asynchronous: call domains_get after domains_verify to read the result.

domains_records, domains_dns, and domains_share apply to custom domains while they are unverified. ShipStatic domains do not require DNS records. Deleting a deployment permanently removes its files, and deleting a domain permanently disconnects it.