How to Deploy Websites Directly from Cursor

AI coding assistants like Cursor are remarkably good at generating complete, working web projects. In minutes you can have a polished HTML page, a dashboard powered by a JSON API, or a static site with routing and styles. The problem? The moment it's done, you're back to copy-pasting files into a separate hosting tool.

With the deplo.sh MCP server, Cursor can deploy its own output. You describe what you want, the AI builds it, and then — in the same conversation — it ships it to a live URL.

What you'll need

• Cursor (any recent version with MCP support)
• A deplo.sh account (free tier works)
• An API key from deplo.sh/dashboard/tokens

Step 1: Add the MCP server to Cursor

Open Cursor Settings → MCP and add a new server entry:

{
  "mcpServers": {
    "deplo": {
      "url": "https://mcp.deplo.sh",
      "headers": {
        "Authorization": "Bearer YOUR_DEPLO_API_KEY"
      }
    }
  }
}

Replace YOUR_DEPLO_API_KEY with the key you copied from your dashboard. Save and restart Cursor.

Step 2: Verify the tools are available

Open the Cursor Agent panel and type:

"What deplo tools do you have available?"

Cursor should list tools like deploy, list_deployments, promote, and archive. If it does, you're connected.

Step 3: Build and deploy in one conversation

Now the fun part. Try a prompt like:

"Build a single-page landing page for my freelance design studio called 'Shape & Form'. Dark background, clean sans-serif typography, hero section with a tagline, and a contact email. Deploy it to deplo.sh when you're done."

Cursor will:

1. Generate the HTML, CSS, and any assets
2. Call the deploy MCP tool with the file content
3. Return a live URL — something like https://shape-and-form.deplo.sh

No terminal. No git push. No Vercel dashboard. Just a URL.

Step 4: Iterate without leaving the chat

The real power is in iteration. Once your project is deployed, you can keep refining in the same conversation:

"Change the hero background to a deep navy gradient and redeploy."

Cursor updates the file and calls deploy again. The URL stays the same, but the content is updated instantly.

Common use cases

Prototyping — Build UI mockups and share them with stakeholders via URL during the conversation.

Client handoffs — Generate a site based on a brief and hand off a live link immediately.

Agent outputs — If your Cursor workflow generates data (reports, charts, summaries), deploy them as browsable HTML rather than saving to disk.

API mocking — Deploy a JSON file as a fake REST endpoint your frontend can call during development.

Tips

• Project names become your subdomain (my-project.deplo.sh), so choose something readable.
• Use the archive tool to clean up test deployments when you're done.
• If you're deploying multi-file sites (HTML + CSS + JS), Cursor can bundle them into a single deploy call.

What's happening under the hood

Every deploy call sends file content over HTTPS to the deplo.sh API, which stores the files at the edge and returns a CDN-backed URL. There's no build step, no container spin-up, and no DNS propagation wait. The URL is live in under two seconds.

This is what makes it useful in an agentic context: the AI can call it mid-conversation without the user needing to switch tools or wait.

Add the deplo.sh MCP server to Cursor in under two minutes: get your API key and follow the MCP integration docs.