ship.page in Claude Desktop

Claude Desktop's config file only speaks stdio, but there are two clean ways to reach ship.page's HTTP endpoint: the built-in custom connector UI, or the mcp-remote bridge that dresses the remote server up as a local one.

What this wires up

Once connected, Claude gets 9 tools: deploy_html, deploy_files, append_files, and drop management (list, claim, restore, delete). Anything Claude writes — a report, a one-pager, a mockup — becomes a live URL it can hand back to you.

Anonymous use works with no key and no account. If you do mint a free sp_ key, drops land on your account where Claude can list and manage them.

Connect it

Option A — custom connector (Claude Pro/Max/Team/Enterprise)

Settings → Connectors → Add custom connector

Name: ship.page
Remote MCP server URL: https://ship.page/mcp

No JSON editing — Anthropic's cloud connects to the endpoint directly. Free tier doesn't show this option; use option B.

Option B — claude_desktop_config.json (any plan, needs Node.js)

{
  "mcpServers": {
    "ship-page": {
      "command": "npx",
      "args": ["mcp-remote", "https://ship.page/mcp"]
    }
  }
}

The file lives at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart the app after saving. Don't paste a "url" field in here — the config validates stdio entries only and silently strips the rest.

The optional API key

Everything above works with zero account — anonymous deploys go live in seconds and that's all you need to share a page. Mint a free sp_ key (sign in at ship.page, dashboard → Keys) and deploys land on your account instead: drops the agent can list, restore and delete, which stay online as long as you keep them, plus named drops — stable, readable URLs that redeploy in place — on paid plans.

Append a header to the bridge args: "args": ["mcp-remote", "https://ship.page/mcp", "--header", "Authorization: Bearer sp_your_key"]. Alternatively use https://ship.page/mcp?apiKey=sp_your_key as the URL — same result, fewer moving parts.

Prompts to try

Prompt

Draft a single-page HTML summary of this conversation and deploy it to ship.page so I can share the link.

Prompt

Turn this spreadsheet data into a small HTML dashboard and put it on ship.page.

Prompt

List my ship.page drops and restore the one called launch-preview.

Questions

Why can't I just paste the URL into claude_desktop_config.json?

That file validates stdio servers only. A "url" entry is silently stripped on load — recent builds can take your other entries with it. Use the connector UI for a direct connection or mcp-remote as the stdio bridge.

mcp-remote fails to launch — what do I check?

It needs Node.js 18+ and npx on the PATH the app sees. Under nvm, point command at the absolute npx path (e.g. ~/.nvm/versions/node/v22.x/bin/npx). The app logs the spawn error in Settings → Developer.

Do I need an API key?

No — anonymous deploys work with no account. A free sp_ key ties drops to your account (dashboard management, restore and claim tools), and they stay online as long as you keep them.

Ship something in the next minute

Paste the config, restart your client, and ask it to deploy a page. No account, no key, no wait — the first URL is free.

MCP & API reference Pricing