ShipStatic
MCP server by ShipStatic
Deploy static websites from your assistant to a live URL, with optional passwords and custom domains.
Connect to ShipStatic
No sign-in needed. Connect with ShipStatic’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to ShipStatic directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/shipstaticAbout
ShipStatic hosts static sites. Through this server an assistant can upload HTML, CSS, JS and other files and get a live URL back. It can also password-protect a site, set an expiry, manage deployments and labels, and connect custom subdomains with DNS setup help.
The hosted endpoint at https://mcp.shipstatic.com needs no install, sign-in or API key for deploying. Without an account, sites are public and expire after 3 days, and a claim URL is returned to keep them. Listing, managing and domain tools need a connected account. A local npm package (@shipstatic/mcp) runs with npx on Node.js 20.19 or newer and takes an optional SHIP_TOKEN API key.
What you can do
- Deploy static site files to an instant live URL
- Password-protect a deployment
- Set an expiry (ttl) on a deployment
- List, inspect, label and delete deployments
- Reserve and link custom subdomains to deployments
- Get DNS records and verify domain DNS
- Check account plan, usage and caps
Tools 15
deployments_uploadWritesDeploy a static site to a live URL; no account needed, optional password and ttl.
deployments_listRead-onlyList deployments with URLs, status, labels and password state.
deployments_getRead-onlyGet deployment details: URL, status, file count, size, labels.
deployments_setCan deleteReplace the labels on a deployment.
deployments_deleteCan deletePermanently delete a deployment and its files.
domains_setCan deleteCreate or update a custom domain, link it to a deployment or edit labels.
domains_listRead-onlyList domains with linked deployment and status.
domains_getRead-onlyGet domain details and status (unverified, unlinked, live, paused).
domains_recordsRead-onlyReturn the DNS records to configure for a domain.
domains_dnsRead-onlyReturn the recorded DNS provider for an unverified domain.
domains_shareRead-onlyReturn a shareable DNS setup URL for whoever manages the DNS.
domains_validateRead-onlyCheck that a domain name is valid and available.
Show 3 more tools
domains_verifyWritesTrigger DNS verification after records are configured.
domains_deleteCan deletePermanently delete a domain.
whoamiRead-onlyShow account email, name, plan, usage and caps.
Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Put this landing page online and give me the link.
Deploy my build output with a password and tell me the password.
Connect www.example.com to my latest deployment.
List my deployments and delete the oldest preview.
Set up
Every client connects to mcp.shipstatic.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http shipstatic https://mcp.shipstatic.com- Start Claude Code and type
/mcp. shipstatic should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it ShipStatic and paste this URL:
https://mcp.shipstatic.com- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://mcp.shipstatic.comand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://mcp.shipstatic.comas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"shipstatic": {
"url": "https://mcp.shipstatic.com"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"shipstatic","type":"http","url":"https://mcp.shipstatic.com"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"shipstatic": {
"type": "http",
"url": "https://mcp.shipstatic.com"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"shipstatic": {
"serverUrl": "https://mcp.shipstatic.com"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add shipstatic --url https://mcp.shipstatic.comOr edit ~/.codex/config.toml directly:
[mcp_servers.shipstatic]
url = "https://mcp.shipstatic.com"Gemini CLI
gemini mcp add --transport http shipstatic https://mcp.shipstatic.comThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"shipstatic": {
"type": "http",
"url": "https://mcp.shipstatic.com"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.shipstatic.com.
Embed
Show ShipStatic in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/shipstatic)<a href="https://mcp.tc/i/shipstatic"><img src="https://mcp.tc/i/shipstatic/badge.svg" alt="ShipStatic on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/shipstatic.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/shipstatic" title="ShipStatic on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/shipstatic.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the ShipStatic card to your site.
Add the mcp.tc card for ShipStatic, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/shipstatic.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="shipstatic"><a href="https://mcp.tc/i/shipstatic">ShipStatic on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/shipstatic)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:36 UTC.
-
New version 2.8.3 (was 2.8.2). Reported by the server.
-
New version 2.8.2 (was 2.8.1). Reported by the server.
-
1 tool changed.
Details, 3 Nov 2026, 20:52 UTC
Changed 1
whoamioutput schema
-
New version 2.8.0 (was 2.7.2). Reported by the server.
-
Server instructions changed.
New server instructions
Details, 23 Oct 2026, 01:30 UTC
Server instructions
BeforeShipStatic 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 deployments_upload 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 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 deployments_upload 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: domains_validate → domains_set with the domain
and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → domains_set…AfterShipStatic 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 deployments_upload 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 deployments_upload 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: domains_validate → domains_set with the domain and…
-
New version 2.7.2 (was 2.7.0). Reported by the server.
-
Server instructions changed.
New server instructions
Details, 20 Oct 2026, 07:39 UTC
Server instructions
BeforeShipStatic deploys static websites instantly. Free, no account required. 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 deployments_upload 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 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 deployments_upload 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: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → domains_se…
AfterShipStatic 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 deployments_upload 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 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 deployments_upload 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: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → domains_set…
-
Server instructions changed.
New server instructions
Details, 19 Oct 2026, 22:33 UTC
Server instructions
BeforeShipStatic deploys static websites instantly. Free, no account required. 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 deployments_upload with the files of your build output. 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 deployments_upload 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: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → domains_set with the deployment to serve. A domain serves nothing until a deployment is linked, so ask the user which one and link i…
AfterShipStatic deploys static websites instantly. Free, no account required. 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 deployments_upload 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 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 deployments_upload 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: domains_validate → domains_set with the domain and the deployment. It is live at once, with no DNS. To add a custom domain: domains_validate → domains_set → domains_records (show DNS records to user) → user configures DNS → domains_verify, only while its `status` is `unverified` → domains_se…
-
New version 2.7.0 (was 2.6.2). Reported by the server.
-
1 tool changed.
Details, 19 Oct 2026, 04:36 UTC
Changed 1
deployments_uploadinput schema
-
New version 2.6.2 (was 2.6.1). Reported by the server.
-
New version 2.5.0 (was 2.4.2). Reported by the server.
-
1 tool changed.
Details, 13 Oct 2026, 22:37 UTC
Changed 1
deployments_uploadThe 10 newest entries show every detail; older ones show names only.
-
New version 2.4.2 (was 2.4.0). Reported by the server.
-
3 tools changed. Server instructions changed.
New server instructions
Details, 12 Oct 2026, 16:30 UTC
Changed 3
deployments_uploaddomains_setdomains_validateThe 10 newest entries show every detail; older ones show names only.
-
New version 2.4.0 (was 2.3.4). Reported by the server.
-
1 tool changed.
Details, 11 Oct 2026, 10:39 UTC
Changed 1
whoamiThe 10 newest entries show every detail; older ones show names only.
-
Tracking started: 15 tools.
FAQ
Can I paste mcp.tc/i/shipstatic into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.shipstatic.com, so your client talks to ShipStatic directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does ShipStatic need an API key or a sign-in?
No. ShipStatic doesn’t ask for an account or key.
Is ShipStatic a remote or a local server?
Remote. ShipStatic hosts it at https://mcp.shipstatic.com, and it speaks Streamable HTTP. There’s nothing to install.
What can ShipStatic do?
It has 15 tools, including deployments_upload, deployments_list and deployments_get. You can deploy static site files to an instant live URL, Password-protect a deployment and set an expiry (ttl) on a deployment.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to ShipStatic?
Yes. ShipStatic’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read ShipStatic’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with ShipStatic. This page was built from ShipStatic’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.