ship.page

Deploy HTML, files, and static sites to a live URL — straight from your AI agent or CI pipeline.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Deploy Html: Deploy one HTML document and get back a live, unguessable https://<slug>.shipped.page/ URL. Anonymous: 10 deploys/min per IP, 10MB body cap, 7-day expiry. Pro ($4/mo): custom or no TTL, n
  • Deploy Files: Deploy a map of path -> content as a multi-file site (must include index.html to serve at the root). Free: up to 100 files per request, 7-day expiry. Pro ($4/mo): up to 900 files, custom
  • List Drops: List drops owned by the authenticated account (requires an sp_ API key; anonymous drops are not listable). Returns slug, url, name, file counts, and expiry, newest first.

What data it sees

Do you need an account

No: the server works without sign-in

Deploy HTML, files, and static sites to a live URL — straight from your AI agent or CI pipeline.

ship.page is the fastest way to publish web content. One tool call gives you a live, shareable URL on a global CDN. No signup, no SDK, no configuration.

What you can do

  • Deploy HTML — hand the agent a page, report, or prototype and get a live link back in seconds
  • Deploy multi-file sites — full static sites (HTML/CSS/JS/assets), including base64-encoded images and binaries
  • Publish from CI — test reports, coverage, Storybook builds, and Lighthouse results as links on every pull request (via the GitHub Action)
  • Manage your drops — list, inspect, and delete everything you've published

Why ship.page

  • Zero friction — works anonymously out of the box; add an optional API key for persistent drops and higher limits
  • Built for agents — structured errors that tell the agent exactly how to proceed, per the latest MCP spec
  • Global by default — every deploy is served from Cloudflare's edge, instantly

Docs: ship.page/docs · Homepage: ship.page

How to connect

How to connect ship.page to Claude

The server address to paste into Claude settings:

https://ship-page--bitgate.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect ship.page to ChatGPT

The server address to paste into ChatGPT settings:

https://ship-page--bitgate.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect ship.page to Cursor

The server address to paste into Cursor settings:

https://ship-page--bitgate.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

deploy_htmlDeploy one HTML document and get back a live, unguessable https://<slug>.shipped.page/ URL. Anonymous: 10 deploys/min per IP, 10MB body cap, 7-day expiry. Pro ($4/mo): custom or no TTL, named drops.
deploy_filesDeploy a map of path -> content as a multi-file site (must include index.html to serve at the root). Free: up to 100 files per request, 7-day expiry. Pro ($4/mo): up to 900 files, custom or no TTL, named drops.
list_dropsList drops owned by the authenticated account (requires an sp_ API key; anonymous drops are not listable). Returns slug, url, name, file counts, and expiry, newest first.
delete_dropPermanently delete a drop owned by the authenticated account (requires an sp_ API key). The URL stops serving immediately and cannot be recovered.
get_limitsShow the ship.page plan matrix (anonymous free tier vs Pro $4/mo vs Team $19/mo) and, when an sp_ API key is present, the caller's current account/plan status.
get_accountShow the authenticated account's plan, subscription status and usage (requires an sp_ API key). Anonymous callers should use get_limits for the static free-tier limits.