Connectors / Cloud, data & infrastructure

ShipStatic

Deploy static sites instantly

Ask your AI to make a page, a report or a small web app, and ShipStatic puts it online. You get a link you can share right away.

What you can ask

Make a one-page site for my bakery and give me a link I can share.
Example path → ·

MCP connector

Server URL: https://mcp.shipstatic.com/gpt
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: ShipStatic deploys static websites instantly. Free, no account needed. Deploy straight away, and bring up an account only when the user asks to see or manage their sites, or to use their own domain.
To deploy: call with the files to publish. If you can run commands and the site is a folder on disk, publish it with the ShipStatic CLI instead: it reads the files from disk. The files need an index.html at the top: it's the page visitors see first, and a site without one is refused. To publish one page, name it index.html. To publish another kind of file, like a PDF, add a small index.html that links to it. The site is live immediately. To make the site private, pass password: that is ShipStatic's built-in password protection, checked before any file is served. When the user asks for a password or a private site, use it, and do not build a password page or script into the site itself. Visitors must unlock before viewing, including on any custom domains pointing at it. Tell the user any password you set, since one they never see locks them out.
Without a connected account, deployments are public and expire in 3 days. The response includes a claim URL — always show the deployment URL and the claim URL to the user so they can keep the site permanently.
Connected to an account, deployments go to that account and never expire — pass ttl (seconds) to for one that expires on its own. Listing, managing, and domain operations need a connected account — call one and the client is told how to connect.
Concepts:
Deployment: an immutable set of files with an instant URL (e.g. happy-cat-abc1234.shipstatic.com). No setup needed.
Domain: a name pointing to a deployment. Optional. A ShipStatic domain (e.g. yourname.shipstatic.com) needs no setup; a custom domain (e.g. www.example.com) needs DNS records. Subdomains only, not apex domains.
To give a deployment a ShipStatic domain: → with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: → → (show DNS records to user) → user configures DNS → , only while its status is unverified → with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it. Read status to know where a domain stands: unverified means its DNS records are not configured yet, unlinked means DNS is right and nothing is published there, live means it serves, paused means the plan has no room for it.

Tools

Reads data9

Changes data2

Deletes or can't be undone4

Skills

1 in the ChatGPT listing

Screenshots

MCP connector

Server URL

https://mcp.shipstatic.com/gpt

OAuth

Protocol

MCP 2025-11-25

Instructions

ShipStatic deploys static websites instantly. Free, no account needed. Deploy straight away, and bring up an account only when the user asks to see or manage their sites, or to use their own domain.

To deploy: call with the files to publish. If you can run commands and the site is a folder on disk, publish it with the ShipStatic CLI instead: it reads the files from disk. The files need an index.html at the top: it's the page visitors see first, and a site without one is refused. To publish one page, name it index.html. To publish another kind of file, like a PDF, add a small index.html that links to it. The site is live immediately. To make the site private, pass password: that is ShipStatic's built-in password protection, checked before any file is served. When the user asks for a password or a private site, use it, and do not build a password page or script into the site itself. Visitors must unlock before viewing, including on any custom domains pointing at it. Tell the user any password you set, since one they never see locks them out.

Without a connected account, deployments are public and expire in 3 days. The response includes a claim URL — always show the deployment URL and the claim URL to the user so they can keep the site permanently.

Connected to an account, deployments go to that account and never expire — pass ttl (seconds) to for one that expires on its own. Listing, managing, and domain operations need a connected account — call one and the client is told how to connect.

Concepts:

Deployment: an immutable set of files with an instant URL (e.g. happy-cat-abc1234.shipstatic.com). No setup needed.

Domain: a name pointing to a deployment. Optional. A ShipStatic domain (e.g. yourname.shipstatic.com) needs no setup; a custom domain (e.g. www.example.com) needs DNS records. Subdomains only, not apex domains.

To give a deployment a ShipStatic domain: → with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: → → (show DNS records to user) → user configures DNS → , only while its status is unverified → with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link it. Read status to know where a domain stands: unverified means its DNS records are not configured yet, unlinked means DNS is right and nothing is published there, live means it serves, paused means the plan has no room for it.