Hosting that works with Claude Code and Cursor agents
A host works with a coding agent such as Claude Code or Cursor when the agent can sign up, deploy, and read the errors by itself, with no dashboard in the way. ShipSite is a static site host made for that. The agent connects over MCP, a CLI, or a REST API, sends the files, and gets back a live HTTPS URL. ShipSite serves static files only, so an app that needs a server or a database needs an application host instead.
We make ShipSite. The set-up steps for Claude Code and Cursor were checked against their own docs on November 19, 2026. Sources are listed at the bottom.
What to check in a host before you give it to an agent
- Can the agent deploy without a browser? An agent works in a terminal or through tool calls. A host that needs clicks in a dashboard stops it.
- Is there an MCP server? Claude Code and Cursor both load MCP servers. With one, a deploy is a tool call and the agent does not have to write the HTTP request.
- How does the agent get credentials? Look for an account the agent can create, sign-in through the browser, or a key with limited rights.
- Can the agent act on an error? The error has to say what went wrong and what to send next.
- What does a forgotten deploy cost? Agents make many previews. Check whether they expire and what each one costs.
- What does the host run? Static files, a build, or server code. This decides more than anything else on the list.
How ShipSite answers each point
| Question | ShipSite |
|---|---|
| Deploy without a browser | POST /v1/sites with a JSON map of files returns a URL that is already serving |
| MCP server | Hosted at https://mcp.shipsite.sh/mcp, or local with npx @shipsite/mcp |
| Credentials | Browser sign-in on the hosted MCP server, or an API key. A deploy-scoped key can manage sites and cannot buy domains, change plans, or manage keys |
| First deploy with no account | POST /v1/sites with no key creates a trial site that lasts 24 hours, up to 50 files and 5 MB |
| Undo a bad deploy | POST /v1/sites/:id/rollback puts the previous version back. A site keeps its 10 newest versions, and each update goes live in one step |
| From a terminal or CI | npx shipsite ./dist, or the Deploy to shipsite.sh action in GitHub Actions |
| Errors | Each error has a code and a message that says what to change |
| Cost of a forgotten deploy | $0.10 per site per day. A site expires after 24 hours unless it is pinned or given a longer ttl |
| What it runs | Static files only, up to 1,000 files and 100 MB per site. No builds and no server code |
Set up ShipSite in Claude Code
Claude Code adds a remote MCP server with one command. To use the hosted ShipSite server with browser sign-in, add it, then type /mcp inside Claude Code and sign in to your ShipSite account. The account has to exist first.
claude mcp add --transport http shipsite https://mcp.shipsite.sh/mcp
To use an API key instead of sign-in, send it as a header:
claude mcp add --transport http shipsite https://mcp.shipsite.sh/mcp \ --header "Authorization: Bearer sk_live_..."
To run the ShipSite MCP server on your own machine:
claude mcp add --env SHIPSITE_API_KEY=sk_live_... --transport stdio shipsite \ -- npx @shipsite/mcp
Set up ShipSite in Cursor
Cursor reads MCP servers from .cursor/mcp.json in a project, or from ~/.cursor/mcp.json for every project. Add ShipSite under mcpServers. This entry uses the hosted server with an API key:
{
"mcpServers": {
"shipsite": {
"url": "https://mcp.shipsite.sh/mcp",
"headers": { "Authorization": "Bearer sk_live_..." }
}
}
}
This entry runs the ShipSite MCP server locally:
{
"mcpServers": {
"shipsite": {
"command": "npx",
"args": ["@shipsite/mcp"],
"env": { "SHIPSITE_API_KEY": "sk_live_..." }
}
}
}
Deploy from an agent without MCP
ShipSite also works from any agent that can run a shell command or send an HTTP request. The shipsite CLI deploys a folder and prints the URL, which fits a project that has just been built:
export SHIPSITE_API_KEY=sk_live_... npx shipsite ./dist
The REST API takes the files as JSON, which fits an agent that has the files in memory:
curl -X POST https://api.shipsite.sh/v1/sites \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"files": {"index.html": "<h1>Hello</h1>"}}'
What a ShipSite account costs an agent's owner
ShipSite charges $0.10 per site per day, prorated daily and billed monthly through Stripe. ShipSite has no free tier. An agent can show a first result on a free trial site that lasts 24 hours; to keep a site, a person adds a card once. One site kept for 30 days is $3. A preview left to expire after 24 hours is $0.10.
When ShipSite is the wrong host for an agent
- The app has a backend. ShipSite runs no server code, no functions, and no database.
- The host has to run the build. ShipSite has no build step. The agent runs the build and deploys the output folder.
- You want a free plan. ShipSite has none.
- The site is larger than 1,000 files or 100 MB. ShipSite refuses it.
For two hosts that do run builds and server code, see ShipSite vs Vercel and ShipSite vs Netlify.
Questions people ask
Does ShipSite work with Claude Code?
Yes. ShipSite has an MCP server, so Claude Code can deploy a site as a tool call. Run claude mcp add --transport http shipsite https://mcp.shipsite.sh/mcp, then type /mcp in Claude Code and sign in to your ShipSite account in the browser. Claude Code can also run the shipsite CLI or call the REST API directly.
Does ShipSite work with Cursor?
Yes. Add ShipSite under mcpServers in .cursor/mcp.json in a project, or in ~/.cursor/mcp.json for every project. Use the hosted server at https://mcp.shipsite.sh/mcp with an Authorization header, or run the @shipsite/mcp package locally with npx and a SHIPSITE_API_KEY environment variable.
Can a coding agent sign up for ShipSite by itself?
Mostly. An agent can deploy one trial site with no account: POST /v1/sites with no key returns a live URL that lasts 24 hours. To keep it, the agent calls POST /v1/accounts with an email address, or the create_account tool, and gets an API key and a Stripe checkout link. A person opens the link once to add a card. After that the key works and the agent needs no dashboard.
Can ShipSite host an app with a backend that Claude Code or Cursor built?
No. ShipSite serves static files exactly as they are sent. ShipSite runs no server code, no database, and no build step. A front end that builds to static files works: the agent runs the build, then deploys the output folder. An app that needs a server needs an application host.
What does ShipSite cost when an agent deploys many sites?
ShipSite charges $0.10 per site per day, prorated daily and billed monthly. There is no free tier, apart from one 24-hour trial site that needs no account. A site expires after 24 hours unless the agent pins it or sets a longer ttl, so a preview that nobody keeps costs $0.10 and then stops. An account can have 1,000 active sites and make 120 deploys an hour.
Try ShipSite
Point your agent at the LLM docs and ask it to deploy something. It will create the account, give you a checkout link, and come back with a URL.
Sources
The Claude Code and Cursor steps on this page come from these pages as they read on November 19, 2026. If something here is out of date, the tool's own page is right and this page is wrong.
- Claude Code: MCP in the Claude Code docs
- Cursor: MCP in the Cursor docs
Claude and Claude Code are trademarks of Anthropic. Cursor is a trademark of Anysphere. shipsite.sh is not affiliated with or endorsed by either of them.