ShipStatic MCP is an MCP (Model Context Protocol) server that lets AI agents instantly deploy static websites. Its core idea is "one URL, your agent can publish."
Purpose The tool is aimed at scenarios that need to publish static websites, landing pages, and prototypes directly from an AI agent. Users only need to give the agent an instruction (such as "publish this with ShipStatic"), and the agent will publish the files and return two links: a live site URL that can be shared immediately, and a claim link. Sites stay online for 3 days by default; opening the claim link keeps them permanently (a free account is required).
Main capabilities
- Publish static websites: deploy without an account and return a live link and a claim link.
- Password protection: you can ask the agent to publish a site with built-in password protection, and visitors must enter the password to view it.
- Account connection: after connecting an account, you can view all published content, bind custom domains, and keep sites online permanently.
- Local deployment: the local package supports deploying folders on your machine (the hosted endpoint only accepts inline files and cannot read local paths).
- Toolset: fifteen tools in total, available on both the hosted endpoint and local installation. deployments_upload can be used without an account, while the other fourteen tools are available after connecting an account (hosted) or setting SHIP_TOKEN (local).
- Pagination: deployments_list and domains_list support limit and cursor parameters, and the response carries a cursor; pass it back to get the next page, and null means the last page.
- Idempotent retries: deployments_upload accepts idempotencyKey to avoid creating duplicate sites when retrying after a timeout.
- Automatic cleanup: deployments_upload accepts ttl (seconds), and after expiration the deployment automatically expires and is reclaimed by the platform, which is suitable for previews and temporary iterations.
How to use Hosted method (recommended): add https://mcp.shipstatic.com to any MCP client. Claude Desktop and claude.ai can paste the URL and save it in "Settings → Connectors → Add custom connector." Clients that support mcp.json, such as Cursor, Antigravity, Windsurf, n8n, and Zed, can also use it. VS Code can install the ShipStatic extension; the server is built in and requires no configuration. Local method: install the npm package @shipstatic/mcp and run it via npx (Node.js 20.19 or higher is required). The configuration needs to set the SHIP_TOKEN environment variable, whose value is an API key (starting with ship-), available for free at my.shipstatic.com/api-key. The key is optional: when not set, the local server behaves the same as the hosted endpoint without a connected account (public site, claim link, 3-day validity).
Use cases
- Quickly publish static websites, landing pages, and prototypes.
- Generate and share website links directly in AI agent conversations.
- Temporary sites that need password protection.
- Scenarios that need to deploy local folders.
- Users who need to manage multiple deployments, custom domains, and permanent sites.
Limitations
- The hosted endpoint cannot read local file paths and can only accept inline files; deploying local folders requires the local package.
- When no account is connected, sites are kept for only 3 days by default and are subject to the rate limits of the shared anonymous pool.
- Deployments with ttl require an account (SHIP_TOKEN locally, a connected account when hosted) and cannot bind any domain.
- Running locally requires Node.js 20.19 or higher.
- Some clients may not yet support OAuth, in which case the local method must be used to configure the token.
This server has been published to the MCP Registry under the identifier com.shipstatic/mcp.
