To deploy a website built in Cursor, you don’t need CI pipelines, a VPS or a deploy config. If it’s a static HTML site, zip the project folder and upload it to Yetty: it converts for free, goes live on a real address in minutes with the design byte-for-byte, and connects to your custom domain through a guided wizard. Then add Yetty’s MCP server to Cursor and you can keep editing the live site from the same editor that built it.

Cursor (and VS Code with an AI sidekick) is where a lot of first websites get built now - you chat, the agent writes files, and an hour later there’s a finished site sitting in a folder. The gap between that folder and "my customers can visit it" is what this guide closes.

Check what you actually built

Open your project. If it’s index.html plus pages, CSS and images - files a browser can open directly - you have a static site, and the rest of this guide is your fast lane. If the agent scaffolded a React, Next.js or Vue app (a package.json, a src/ folder, a build step), that’s an application, and it belongs on a developer platform built for that. Yetty serves static and server-rendered HTML byte-true; it doesn’t host JS app builds, and we’d rather tell you that here than after an upload. Tip for next time: asking Cursor for "plain static HTML, no framework" gets you a site that’s faster and deployable anywhere.

Ship it: zip, upload, live

The whole deployment, no DevOps vocabulary required:

  1. Zip the site folder with index.html at the top level - not buried inside a subfolder.
  2. Upload it to Yetty. Conversion is free; in minutes the site is live on yourname.yetty.site with SSL, exactly as Cursor wrote it - no rebuild, no template, byte-for-byte your design.
  3. Connect your domain when ready: the custom domain wizard tells you the exact DNS records to set, verifies them, and flips the site over with SSL handled.

Along the way you quietly gain the production layer you’d otherwise assemble by hand: your contact forms wired into a leads inbox, SEO and sitemap handled, and every update saved as a version with one-click rollback - nothing you push can ever be lost.

The good part: production stays inside Cursor

Yetty speaks MCP, and Cursor is an MCP client - so your editor gets deploy-and-edit powers over the live site. Add this to .cursor/mcp.json (create the key at app.yetty.ai, under API Keys):

{"mcpServers":{"yetty":{"url":"https://mcp.yetty.ai/","headers":{"Authorization":"Bearer YOUR_KEY"}}}}

From then on, deployment is a sentence in the agent panel. "Send this site to Yetty" pushes the exact files - no zip step at all. "Change the pricing headline" edits the live page as a staged draft. "Any leads this week?" reads your inbox. "Roll back that last change" does exactly that. The loop you liked while building - describe, see it happen - becomes how you run production too. The full setup for every editor is on the connect your AI page.

Why not just a static host?

You could push the folder to a classic static host - and if you enjoy configuring form services, redirect rules and analytics snippets, that path works. The trade-offs are real, though: forms don’t receive messages, edits mean code-and-push forever, and nobody non-technical can ever touch the site. We compared the options honestly in how to host an AI-generated website. And if your site started as a one-page Claude artifact rather than a Cursor project, there’s a dedicated path for that too: publishing a Claude artifact as a website.

From folder to production is minutes, not a weekend. Connect Cursor to Yetty and make "deploy" a thing you say, not a thing you configure.

FAQ

How do I deploy a static website from Cursor?

Zip the project folder with index.html at the top and upload it to Yetty - it’s live on a free yetty.site address in minutes. With the Yetty MCP server added to Cursor, the agent can send the files directly instead.

Can Cursor edit a website that’s already live?

Yes - add Yetty’s MCP server to .cursor/mcp.json and Cursor’s agent can update text, add pages and roll back changes on the live site, with every change versioned.

Do I need a server or CI pipeline to publish a Cursor-built site?

No. For a static HTML site there’s nothing to provision or configure - upload once, and hosting, SSL, forms and versioning are handled for you.