ship.page in Cursor: one mcp.json entry
Cursor connects to remote MCP servers over Streamable HTTP with a single url field — no command, no runtime, no bridge. Add the entry, reload, and the agent gains nine deploy tools it can call mid-task.
What this wires up
The ship.page MCP server exposes 9 tools: deploy_html for a single page, deploy_files for a whole file map, append_files to extend an existing drop, plus list, claim, restore and delete for managing drops. Anonymous use works with no key at all.
Tools fire in Agent mode, not plain chat. Cursor asks for approval before each call unless you allow the server to run automatically.
Connect it
.cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"ship-page": {
"url": "https://ship.page/mcp"
}
}
}Project scope travels with the repo; global scope puts the server in every workspace. Open Settings → MCP after saving — the server should show a green dot with its tool list.
The optional API key
Everything above works with zero account — anonymous deploys go live for 7 days and that's all you need for quick shares. 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, 30-day expiry on the free plan, and named drops — stable, readable URLs that redeploy in place — on paid plans.
Add a headers block to the same entry: "headers": { "Authorization": "Bearer sp_your_key" }.
Prompts to try
Prompt
Build a one-page pricing comparison for our two tiers as a single HTML file and deploy it to ship.page so I can share it.Prompt
Generate the coverage report, then use ship-page to deploy the folder and drop the URL in the PR description.Prompt
Use ship-page to list my drops and tell me which ones expire this week.Questions
Do I need an account or API key?
No. Anonymous deploys work out of the box and live for 7 days. A free sp_ key puts drops on your account — manageable from the dashboard, 30-day expiry, and named drops on paid plans.
The server shows a red dot — what now?
Check the JSON parses (a trailing comma kills the whole file silently), then reload the window. If both a project and global mcp.json define the same name, the project entry wins — edit the right one.
Why isn't the agent calling the deploy tools?
MCP tools only run in Agent mode, not in plain chat. Also check Settings → MCP: servers can be toggled off individually, and too many enabled servers makes tool selection worse.
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.