Skip to main content
Glama

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, Devin Desktop, 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.

Related MCP server: deloc-mcp

Keep your sites with a free account

Everything above works with no account. A free account keeps your sites for good, gives you a ShipStatic domain like yourname.shipstatic.com, and shows you everything you've published in one place. A custom domain like www.example.com needs a paid plan.

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

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. 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

Surface

Reach it

CLI and SDK

npx @shipstatic/ship ./dist

VS Code

Search "ShipStatic" in the Marketplace

Plugin

Install it in Cursor, Claude Code, Codex or Gemini CLI

OpenCode

opencode plugin add opencode-shipstatic

Antigravity

agy plugin install https://github.com/shipstatic/antigravity

n8n

Search "ShipStatic" in n8n's node panel

GitHub Action

shipstatic/action@v3

Agent Skill

npx skills add shipstatic/plugin

License

MIT

Available Tools

15 tools
deployments_deleteDelete DeploymentB
DestructiveIdempotent
Inspect

Permanently deletes a deployment and its files.

Inputs: deployment (required). Returns: status, deployment

deployments_getGet DeploymentA
Read-only
Inspect

Get deployment details including URL, status, file count, size, labels, and password protection state.

Inputs: deployment (required). Returns: url, via, size, files, +8 more

deployments_listList DeploymentsA
Read-only
Inspect

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.

Inputs: limit, cursor. Returns: cursor, deployments

deployments_setUpdate Deployment LabelsA
Destructive
Inspect

Update deployment labels. Replaces all existing labels.

Inputs: labels (required), deployment (required). Returns: url, via, size, files, +8 more

deployments_uploadDeploy Static SiteAInspect

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 also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass password to make the site private.

Inputs: path (required), ttl, labels, password, +1 more. Returns: url, via, size, claim, +9 more

domains_deleteDelete DomainA
DestructiveIdempotent
Inspect

Permanently deletes a domain.

Inputs: domain (required). Returns: domain

domains_dnsGet DNS ProviderA
Read-only
Inspect

Returns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate.

Inputs: domain (required). Returns: dns, domain

domains_getGet DomainA
Read-only
Inspect

Get domain details including URL, linked deployment, labels, and status: the one word saying what the domain needs from its owner (unverified, unlinked, live, paused).

Inputs: domain (required). Returns: url, links, domain, labels, +8 more

domains_listList DomainsA
Read-only
Inspect

List all domains with their URLs, linked deployment, and status. The response's cursor is null on the last page; pass it back as cursor to fetch the next.

Inputs: limit, cursor. Returns: cursor, domains

domains_recordsGet DNS RecordsA
Read-only
Inspect

Returns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.

Inputs: domain (required). Returns: apex, domain, records

domains_setSet DomainA
Destructive
Inspect

Create or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. For a custom domain, domains_records then returns the DNS records to configure.

Inputs: domain (required), labels, deployment. Returns: url, links, domain, labels, +9 more

domains_shareShare DNS SetupA
Read-only
Inspect

Returns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.

Inputs: domain (required). Returns: url, domain

domains_validateCheck Domain AvailabilityA
Read-only
Inspect

Check if a domain name is valid and available before creating it. Returns the normalized form and availability.

Inputs: domain (required). Returns: valid, reason, available, normalized

domains_verifyVerify Domain DNSAInspect

Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read the domain again with domains_get to learn the verdict, since its status has not moved yet when this returns. A verified domain serves nothing until a deployment is linked with domains_set.

Inputs: domain (required). Returns: domain

whoamiShow AccountA
Read-only
Inspect

Returns your email and name, and the account's plan, usage and caps.

Inputs: no named parameters. Returns: caps, name, plan, email, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    The CRUD sets for domains and deployments are clearly distinct, and validate/verify/set are well separated by their preconditions. The one soft spot is the trio domains_records, domains_dns, and domains_share, which all share the same 'custom domains only, while unverified' trigger and could be confused by an agent deciding which DNS helper to call.

    Naming Consistency4/5

    Almost everything follows a clean resource_verb snake_case pattern (domains_list/get/set/delete, deployments_upload/list/get/set/delete). The only deviations are the unprefixed whoami and the upload-vs-set verb split for deployment creation vs. update, both of which remain readable.

    Tool Count4/5

    15 tools is at the upper edge of the comfortable range but each maps to a real operation in the deploy-and-domain workflow. The DNS follow-up helpers (records/dns/share) feel slightly granular and could arguably be folded, but nothing is redundant filler.

    Completeness5/5

    Deployments have upload/list/get/update/delete, and domains have a full lifecycle from validation through set, DNS records, verification, sharing, and deletion, plus whoami for account context. The only minor limitation is that deployments_set touches labels only (password/relink not updatable), which is a small gap rather than a dead end.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Deloc — deploy static sites from AI coding agents. Say "deploy this to Deloc" in Claude Code or Cursor and get a live URL back without leaving your editor.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.
      2
      MIT