What is the ship.page remote MCP server?
The ship.page remote MCP server is a hosted Model Context Protocol endpoint at https://ship.page/mcp, so AI assistants can connect to it without installing or running anything locally.

@Bitgate
Basic information
Transport
Streamable HTTP
Authentication
None
Category
Developer Tools
Author
Bitgate
Submitted by
Bart Pelle
Throw HTML at an API, get an unguessable URL back. Zero-config remote MCP server — your agent deploys pages, sites and CI reports in one call. Free, no signup needed.
https://ship.page/mcpclaude mcp add ship-page --transport http https://ship.page/mcpDeploy one HTML document and get back a live, unguessable https://<slug>.ship.place/ URL. Anonymous: 10 deploys/min per IP, 10MB body cap, 30-day expiry. Pro ($4/mo): custom or no TTL, named drops.
Deploy a map of path -> content as a multi-file site (must include index.html to serve at the root). Anonymous: up to 100 files per request, 30-day expiry (90 days once signed in). Pro ($4/mo): up to 10,000 files, custom or no TTL, named drops.
Add files to a drop owned by the authenticated account (requires an sp_ API key and an active subscription): up to 10,000 files per drop in total, and existing paths are overwritten. The drop keeps its current expiry and password protection.
List drops owned by the authenticated account (requires an sp_ API key; anonymous drops are not listable). Returns slug, url, name, file counts, expiry and password_protected, newest first.
Attach an anonymously deployed drop to the authenticated account using its one-time claim token (spc_..., returned once by deploy_html/deploy_files). Claiming extends the drop to the free-account lifetime (90 days) and can revive an offline drop during its 30-day private recovery window. Claimed drops become listable, deletable, and — on paid plans — redeployable via named drops. Requires an sp_ API key.
Bring back an expired drop owned by the authenticated account while its files are still retained (requires an sp_ API key), up to 90 days past expiry. Free accounts get the drop back at the 90-day lifetime; on a paid plan the restored drop never expires again.
Permanently delete a drop owned by the authenticated account (requires an sp_ API key). The URL stops serving immediately and cannot be recovered.
Set or rotate the shared password on a drop you own. Requires an sp_ API key and active paid Pro/Team; unavailable billing returns an error, not a public drop. Visitors unlock in their browser. Never put the password in a URL.
Remove password protection from a drop you own, making it readable by anyone with its URL. Requires an sp_ API key; works even after your paid subscription lapses.
Show 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.
Show 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.
Throw HTML at an API, get back a live URL. ship.page is the fastest way for an AI agent to put content on the public internet — deploy pages, multi-file sites, and CI reports in one call, then hand your human a link. Free, no signup, no OAuth dance.
*.shipped.page subdomain, mounted at root so absolute paths just workPOST your markup and get JSON back with a live url:
curl -X POST https://ship.page/deploy \
-H "Content-Type: text/html" \
--data-binary @report.html
Three body formats: raw HTML, a JSON path → content files map (base64 for binaries), or a full zip of a build folder. Anonymous drops live for 7 days, no account required.
Deploy and manage drops straight from your agent: deploy_html, deploy_files, list_drops, claim_drop, delete_drop, get_limits — plus structured JSON errors with human-readable hints your agent can relay verbatim when something's plan-gated.
Auth is optional pass-through: no key = anonymous deploys, Authorization: Bearer sp_… = the tools act as that account (30-day drops, higher limits, named drops on Pro).
Config:
{
"mcpServers": {
"ship.page": { "url": "https://ship.page/mcp" }
}
}
Full API also published as an OpenAPI 3.1 spec at ship.page/openapi.json. Docs: ship.page/docs/agents
The ship.page remote MCP server is a hosted Model Context Protocol endpoint at https://ship.page/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://ship.page/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
No. ship.page's MCP server does not require authentication — you can connect directly with the endpoint URL.
ship.page exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Ideate, create, and deliver with Adobe pro tools
Pharmaceutical drug & clinical trial intelligence
Discover, evaluate, and buy solutions for the cloud
Official 42min MCP server: let Claude, ChatGPT, Cursor or any MCP client manage your meeting scheduling. Check availability, find free slots, book, cancel and reschedule meetings, manage recurring series, secret booking
Search and read current AWS documentation, check regional availability and load AWS agent skills, with no AWS account needed.
Comments