Deploy Cursor

Deploy Cursor sites with VibeDeploy

Name: VibeDeploy
Brand: VibeDeploy

Cursor writes the project; publishing it is up to you. Install VibeDeploy in Cursor with one link, sign in once, and Agent can ship the build to servers in Belgium, attach your domain and run the backend next to it without leaving the editor.

Deploy your Cursor site Add to Cursor See pricing

Why VibeDeploy for Cursor

A Cursor project ends up in a repository or on your laptop, and the step to a public URL usually means a second dashboard. VibeDeploy turns that step into tools Cursor's Agent can call: deploy, read the live files, fix a line, redeploy, add a domain or start a database. Cursor asks before each tool call by default, so you see every action before it runs.

bolt

One-click install link

The Add to Cursor link writes the server entry for you, and the only setting is the endpoint URL. Sign-in runs through OAuth in the browser, so mcp.json never holds an API key.

edit_note

Fixes after launch, same chat

Agent can read and search the files that are live and change exact lines with apply_edits, which go live at once, or edit the stored source and rebuild with build_and_deploy. A typo on the live site becomes a one-message fix.

dns

Static or full stack

Static builds are served straight from Belgium. When the app needs its Node server, Postgres or Redis, Agent starts them as gVisor-isolated containers next to the site with deploy_app: up to 6 services, 2 CPU and 2 GiB per site.

How to deploy a Cursor site

1
Install VibeDeploy with the Cursor link
Open the install link below in your browser. Cursor opens and prompts you to install the server, with the VibeDeploy endpoint already filled in.
```
https://cursor.com/install-mcp?name=vibedeploy&config=eyJ1cmwiOiJodHRwczovL21jcC52aWJlZGVwbG95LmJlL21jcCJ9
```
2
Or add it to mcp.json
For every project, edit ~/.cursor/mcp.json in your home folder; for one repository, use .cursor/mcp.json in its root. A remote server needs nothing but its url.
```
{
  "mcpServers": {
    "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" }
  }
}
```
3
Sign in to VibeDeploy
When Cursor asks you to log in to the server, the VibeDeploy sign-in opens in your browser. Google, GitHub or Microsoft is the quickest route, and a new account starts a 14-day trial without a card.
4
Ask Agent to deploy
Open Agent in the side pane (Cmd+I on macOS) and try: "Run the production build, deploy the output folder to VibeDeploy as cursor-demo and give me the URL." Cursor asks before each tool call unless you let the tool run automatically.
5
Attach your domain
Ask "Connect www.example.com to cursor-demo." Agent returns the DNS records to set at your registrar and checks them with verify_custom_domain; the certificate is issued automatically.
6
Prefer git?
Connect the repository on GitHub and each push triggers a build on VibeDeploy: npm run build by default, then the first of dist, build, out or public goes live. For a one-off release, drop the build folder into the dashboard.

Guides for Cursor

Cursor hosting at a glance

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

Feature	Cursor default / generic alt	VibeDeploy
Public URL	Set up a host yourself	Agent deploys and returns it
Install in Cursor	Depends on the host	One-click link, OAuth sign-in
Edit the live site	Rebuild and redeploy by hand	Agent reads, patches and redeploys
Backend and database	Depends on the host	Containers next to the site
Hosting location	Depends on the host	Belgium (EU)

Common questions about deploying Cursor

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

Install the VibeDeploy MCP server with the Add to Cursor link, sign in once, and ask Agent to deploy the project. It runs the build, uploads the output and answers with a live URL; a custom domain with automatic SSL is one more request. GitHub build on push and dashboard upload work if you would rather not use MCP.

Can Cursor deploy a Next.js app with server-side rendering?expand_more

Yes. A static export or SPA build is served as files. For server-side rendering or API routes, Agent runs the Next.js server as a container next to the site with deploy_app, in a gVisor sandbox with up to 6 services, 2 CPU and 2 GiB of memory per site. Container data is not yet included in snapshots.

Where do I see what the VibeDeploy server is doing?expand_more

Cursor writes MCP traffic to its Output panel: open it (Cmd+Shift+U on macOS) and pick MCP Logs. The server can be switched off and on under Customize. For container apps, ask Agent to call get_app_status, which returns their status and logs.

Cursor has checkpoints. Do I still need deploy history?expand_more

Yes, they cover different things. Checkpoints undo Agent's edits to files on your machine and never touch the live site. VibeDeploy keeps every deploy as a version with a restore point before each one, and you restore an earlier version in one click from the dashboard within your plan's window: 3 days on the trial, Solo and Maker, 7 on Studio.

Does mcp.json need an API key?expand_more

No. VibeDeploy uses OAuth 2.1 with PKCE: Cursor registers itself, you sign in once in the browser, and Cursor keeps the token. Access is limited to the team you approve, and access tokens expire after an hour.

Is staging available?expand_more

On Studio and Business. A site there gets a staging copy at its own address that you promote to production from the dashboard; the MCP tools always deploy to the live site.