Deploy Cursor

Deploy Cursor sites with VibeDeploy

Name: VibeDeploy
Brand: VibeDeploy

Cursor is the editor most AI-native developers use. It does not host what you build. VibeDeploy connects to Cursor over MCP, so the agent ships your site to a real EU-hosted URL with a custom domain and automatic SSL.

Deploy your Cursor site See pricing

Why VibeDeploy for Cursor

Cursor is where you build, not where your site lives. To take what you build to production you need a deploy target. VibeDeploy slots in as the EU-resident host, connected to Cursor over the Model Context Protocol, so deploys happen without leaving the editor.

cable

Native MCP integration

Cursor speaks the Model Context Protocol. Connect VibeDeploy's MCP server once and Cursor's agent can deploy, list your sites, and manage domains directly from the editor.

settings_suggest

Framework detection

Vite, static Next.js export, Astro, SvelteKit, plain HTML. VibeDeploy detects the build command and output directory, so most projects deploy with no extra config.

shield_lock

EU hosting, flat pricing

Served from Belgium with automatic SSL and custom domains on every plan. Flat per-plan pricing, no per-seat fees and no per-bandwidth metering.

How to deploy a Cursor site

1
Build your app in Cursor
Iterate normally. When the preview works, you're ready to ship. VibeDeploy serves static and SPA output: Vite, static Next.js export, Astro, SvelteKit, or plain HTML.
2
Connect the VibeDeploy MCP server
Start a 14-day free trial at vibedeploy.be (no credit card). In Cursor, open Settings, then MCP, and add the VibeDeploy server. A browser window opens once to authorise it with your VibeDeploy account.
```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" }
  }
}
```
3
Tell Cursor's agent to deploy
Ask in plain language: "Deploy this site to VibeDeploy." The agent calls the deploy tool, uploads your build, and replies with the live URL. No manual upload, no copy-paste back to a browser.
4
Add a custom domain
In site settings, add your domain and point a CNAME at VibeDeploy. SSL provisions automatically, usually within 60 seconds. Until then the site is live at name.vibedeploy.be.
5
Prefer not to use MCP? Two other ways
Connect a GitHub repo so every push builds and redeploys automatically, or drag your build output into the dashboard. Same hosting, your choice of workflow.

Cursor hosting at a glance

How Cursor's default hosting and a generic alternative compare to VibeDeploy.

Feature	Cursor default / generic alt	VibeDeploy
Editor integration	None / manual	Native MCP server
Hosting location	Varies	EU (Belgium)
Framework auto-detect	Yes (Vercel/Netlify)	Yes
Redeploy on git push	Varies	Yes
Per-team pricing	Per-seat	Flat per plan

Common questions about deploying Cursor

How do I deploy a project from Cursor to a live URL?expand_more

Add the VibeDeploy MCP server in Cursor, authorise it once, then ask the agent to deploy your project. It builds the static or SPA output and returns a live URL. You can then connect a custom domain with automatic SSL. GitHub build-on-push and dashboard upload are available if you prefer not to use MCP.

Does VibeDeploy support Next.js apps from Cursor?expand_more

Static export and SPA-mode Next.js work out of the box. Server-side rendering and API routes require running the Next.js server, which is not part of VibeDeploy's static-edge model. For SSR-heavy Next.js, use a server host; for static-export Next.js, just deploy.

How does the Cursor integration actually work?expand_more

Through MCP. Cursor has native Model Context Protocol support, so once you add the VibeDeploy server and authorise it, the deploy tools become available to Cursor's agent. You ask it to deploy in plain language and it handles the API calls for you.

Is there a command-line tool to install?expand_more

No, and you don't need one. You deploy by asking Cursor's agent through the MCP server, by connecting a GitHub repo for build-on-push, or by uploading from the dashboard. There is nothing to install globally.

Can I deploy a private staging environment?expand_more

Yes, on the Studio plan and above. Each site gets a parallel staging URL on its own subdomain, password-protected by default.