Connect Cursor to VibeHost via MCP and deploy to a live URL from inside the editor.

Cursor speaks MCP natively. Once it is connected, you describe what you want and Cursor calls the VibeHost tools it needs to deploy, promote, or manage domains.

Connect

Install button

Manual setup

⌘ + Shift + J to open Cursor Settings.
Select Tools & MCPs.
Select New MCP Server.
Paste the following configuration:

{
  "mcpServers": {
    "vibehost": {
      "url": "https://api.vibehost.com/mcp"
    }
  }
}

The first tool call triggers an OAuth flow in your browser. After approval, Cursor can call every VibeHost MCP tool. See the MCP guide for the tool cheatsheet.

First deploy

Open your project in Cursor, then in the chat panel (⌘ + L):

Deploy this directory to VibeHost as a new app called my-cursor-app. It's a Vite + React build.

Cursor:

Reads your project (sees package.json, vite.config.ts).
Asks you to confirm running npm install + npm run build.
Creates the my-cursor-app app.
Uploads ./dist and deploys it.
Returns the URL.

The tool calls behind steps 3 and 4 are described once, in Choosing an upload path.

If you've never connected before, OAuth runs once (browser pop-up) between steps 2 and 3.

Common prompts

One-shot deploy

"Use VibeHost to deploy this Vite project as my-app." Cursor creates the app, uploads the build and deploys it via MCP.

Preview channels

"Deploy this to a pr-${number} channel on VibeHost so I can share the URL with my team."

Cross-app ops

"List all my VibeHost apps and tell me which ones haven't been deployed in the last 30 days."

Debug a failing deploy

"Look at the latest deployment logs for my-app and tell me why it's not serving traffic."

Make it shareable

"Set my-app to public and create a share link valid 7 days."

Custom domain

"Add www.example.com as a custom domain on my-app, tell me what CNAME to add, then verify it once I confirm DNS is set."

Gotchas

@VibeHost mention triggers tool routing reliably. If Cursor is calling a different tool than you expect, prefix your prompt with @VibeHost ... (the MCP server name).
YOLO mode (auto-run without confirmation) bypasses tool prompts. Useful for repetitive deploys, dangerous for destructive ops. Toggle in Settings → MCP.
Re-auth after long gaps. Refresh tokens are 30 days; after that you'll see UNAUTHENTICATED on the next tool call. Cursor re-prompts the OAuth flow.
--build server not needed. Cursor builds locally. Your machine runs npm run build, and MCP receives only the artifact.

Tips

To pin your default workspace, tell Cursor's chat "From now on use my acme workspace on VibeHost". Cursor then appends workspaceId to later tool calls.
Save common prompts as Cursor rules (.cursorrules or per-project) so "ship to staging" or "preview this PR" become one-shot.
If a deploy hangs, ask Cursor to run vibehost doctor --json in a terminal. It diagnoses auth, API reachability, and config issues.

Deploy from Cursor