Cursor + xCloud

Deploy from Git with Cursor on xCloud

Deploying from Git with Cursor means asking the agent in your editor to ship the project you have open, and letting xCloud detect the app, preview the site, create it after your approval and check the live URL without you leaving the window.

Skill: xcloud:deploy
Toolsets: sites, servers, integrations
Free with every xCloud account

Set up Cursor All Cursor guides

YouDeploy this repo to Frankfurt on a staging hostname. Dry run first.

git_detectread-only

AgentNext.js app on main, remote github.com/acme/shop. package.json builds with npm run build. xCloud suggests the same command and a free staging hostname. Your last commit is pushed. Create the site?

YouYes.

servers_sites_git_autoneeds approval

AgentDeployed. SSL is issued and the staging URL answers 200. Dashboard link is in the panel.

Last updated: October 2026. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.

Setup

How Do You Set Up Cursor to Deploy from Git on xCloud?

Connect Cursor once; every job on this account uses the same connection. Then ask in plain words.

1
Add xCloud to mcp.json with the compact URL
Cursor stops at 40 tools per server, and the full xCloud server advertises one tool per customer-facing operation, so start with the compact profile: five tools that still reach every operation. Put this in ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/mcp?profile=compact"
    }
  }
}
```
2
Or add it from Cursor's MCP settings
Cursor's docs manage MCP servers from the Customize page. Add a new server there and paste the compact URL instead of editing the file. Use the plain https://app.xcloud.host/mcp URL only if your Cursor version loads every tool.
URL
```
https://app.xcloud.host/mcp?profile=compact
```
3
Sign in to xCloud
Cursor supports OAuth for remote servers and shows a login prompt next to xcloud. Click it, approve the teams and choose Read-only or Full access in the browser, then ask this to confirm.
Prompt
```
Who am I on xCloud?
```

Check it worked

Then ask Cursor for the job itself, for example:

Prompt

Deploy this repo to my Frankfurt server on a staging hostname. Show me the dry run first.

In practice

How Does Deploy from Git Work from Cursor?

In Cursor the agent already has your project in front of it: the file tree, the open branch, the package.json or composer.json and the build scripts. When you type deploy this to Frankfurt in the agent panel, it reads the Git remote from the repository, calls git_detect through the xCloud connection and compares what xCloud suggests with what your files really declare. If xCloud proposes npm run build and your scripts table says otherwise, the agent tells you before anything is created. That check is the practical gain over a dashboard form, where you would type the commands from memory.

Remember that xCloud deploys from the Git remote, not from the files in your editor. Uncommitted edits and unpushed commits are not part of the deploy, so ask Cursor to commit and push first if the change you care about is still local. Because Cursor stops at 40 tools per server, the xcloud entry in mcp.json should use the compact URL. The agent then works through five tools, two for searching and three for running operations, and still reaches git_detect, the dry run and the create call. Cursor shows each call in the panel, you answer one yes at the dry run, and the agent confirms the create, follows the site status until it is terminal and fetches the address before it reports success.

The editor is also where a failed deploy is cheapest to fix. When the build breaks, Cursor reads xCloud's deployment diagnosis, which names the failing step and quotes the log, and opens the file that caused it. A wrong build command or web root can be corrected on the same site through a retry. A real code error, such as a missing dependency or a TypeScript failure, you fix in the editor, push and redeploy. The loop of read the log, change the file, push and retry stays in one window.

Cursor specific: The deploy reads the Git remote, so anything uncommitted or unpushed in your editor is not deployed, and Cursor will not warn you unless you ask it to check. Keep ?profile=compact on the xcloud URL in mcp.json, because the full server advertises one tool per customer-facing operation and Cursor stops at 40. If the agent cannot find the deploy tools, open Cursor's MCP settings and confirm xcloud shows as logged in.

What xCloud does for deploy from git

xCloud detects the app in the repository, previews the site it would create with a dry run, creates it once you approve, polls the deployment to a terminal state and checks the live URL. A failed deploy gets a diagnosis and a corrected retry on the same site, never a delete and recreate.

Pick the team and server. The agent uses the server you name. If you name none it lists provisioned servers and asks; it never picks one silently. Node.js, PHP and static builds need an Nginx or OpenLiteSpeed server; anything else needs a Docker server.
Detect the repository. git_detect reads the default branch, the app type (WordPress, Laravel, custom PHP, Node.js or Lovable), the web root, suggested install, build and start commands, repository access and server compatibility. Detection creates nothing.
Choose the address. With no domain the agent asks xCloud for a free staging hostname. With a live domain it checks whether the zone is on a connected Cloudflare account, in which case xCloud writes the DNS record and certificate itself.
Dry run, then one approval. The agent sends the create request with dry_run set to true and shows you the resolved configuration: app type, URL, branch, commands, runtime version and every warning. Then it asks once, naming the server and the URL, before sending the same body with confirm set to true and an idempotency key.
Poll and verify. A 202 means queued, not deployed. The agent polls the site status until it is terminal, reports each real step change, reads failed_steps and the SSL block, and fetches the URL before it calls the site live.
Recover if it fails. On a failed deploy the agent reads the deployment diagnosis, proposes a fix from the correctable fields, and retries on the same site with your approval. Two failed retries with the same classification stop the loop and hand you the dashboard link.

Reference

Deploy from Git Settings and Limits on xCloud

The facts Cursor works within when it deploys from Git. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Supported app types	WordPress, Laravel, custom PHP, Node.js and Lovable on native servers; Dockerfile and Compose apps, including Python, Go and Rust, on Docker servers
Repository sources	Public HTTPS URLs, repositories on a connected GitHub, GitLab or Bitbucket provider, and private SSH repositories with a read-only deploy key
Private repositories	The agent prepares a deploy key on the server, you add the public key to the repository, xCloud verifies it. A private key or personal token never goes in the request
Preview	dry_run: true returns the would_create block and consumes no idempotency key
Idempotency	The create call carries an Idempotency-Key, so a retried request cannot create a duplicate site. A new deployment needs a new key
Deployment states	deployed, failed or cancelled once terminal is true; failed_steps can be non-empty on a deployed site and must be read
Node.js versions	The Node version is server-wide, not per site; changing it can affect other apps on the server
Redeploys	A redeploy runs git reset --hard and git clean -df in the site directory, so uncommitted server-side changes are lost. Supply environment values through env_file_content, not files in the checkout
Staging environments	Available for Git sites on paid plans through the API; WordPress staging stays a dashboard step
Agentic servers	An OpenClaw, Hermes, Paperclip or DeepSeek Harness server hosts only the site created at provisioning; a second site is refused

Rules Cursor has to follow

Creating a site is billable and stops for your approval; detection and the dry run never create anything.
The agent explains every detection warning before asking, and a repository access problem is never worked around by naming an app type by hand.
A deployed state is not proof the application works: the agent fetches the URL and reads failed_steps first.
A failed site is retried in place with corrections; it is never deleted and recreated to retry.
Changing a live site's domain after creation, databases and server resizing are dashboard steps; the agent gives you the path and the dashboard link xCloud returned.

Example prompts

What Can You Ask Cursor to Do for Deploy from Git?

Type these as written and swap in your own repository, site and server names. Reads and routine actions such as backups, cache purges, PageSpeed scans and vulnerability scans run straight away; creating, deploying, updating, rebooting, deleting, buying or starting a broken-link scan stops and asks first.

Prompt

Deploy this repo to my Frankfurt server on a staging hostname. Show me the dry run first.

Prompt

The xCloud build for this project failed. Read the diagnosis, fix whatever is wrong in the repo, push it and retry on the same site.

Prompt

Check that main is pushed, then deploy the latest commit to the staging site and tell me when the URL answers 200.

Prompt

Deploy https://github.com/acme/shop to my Frankfurt server and show me the dry run before creating anything.

Prompt

Deploy the private GitLab repository connected to my team on a staging hostname.

Prompt

Scan the docker-compose.yml in github.com/acme/api and tell me which services and ports xCloud would use.

Prompt

Create a staging environment from the feature/checkout branch of the API site.

Prompt

Deploy the latest commit of the shop site after showing me what will change.

Prompt

The last deploy of the API site failed. Diagnose it, fix the build command and retry on the same site.

Cursor and Deploy from Git: Frequently Asked Questions

What people ask before they let Cursor deploy from Git through xCloud.

Does Cursor deploy the files in my editor or the Git repository?

The Git repository. xCloud clones the repository from its remote, so uncommitted changes and unpushed commits are not included. Ask Cursor to commit and push before you ask it to deploy.

Does the compact URL still let Cursor deploy a repository?

Yes. The compact profile serves five tools, two for searching and three for running operations, and they reach every customer-facing xCloud operation including repository detection and the site create call. The agent uses them to find and run the deploy steps.

Does the agent create the site as soon as I give it a repository URL?

No. It detects the repository and runs a dry run first, shows you the resolved configuration, and asks once. Only after you approve does it send the create call with an explicit confirmation and an idempotency key.

Can an agent deploy a private repository through xCloud?

Yes. Either the repository is on a Git provider connected to your xCloud team, or the agent prepares an SSH deploy key on the server for you to add to the repository. A private key or a personal access token is never sent in the request.

What does a 202 response mean during a deploy?

That xCloud queued the deployment. The agent polls the site status until it is terminal and reports deployed, failed or cancelled, then checks failed_steps and fetches the URL before calling the site live.

What happens when a deploy fails?

The agent reads the deployment diagnosis, which classifies the failing step and quotes the relevant log lines, proposes a fix from the fields xCloud lets it correct, and retries on the same site after your approval. It never deletes and recreates the site to retry.

Which servers can take a Git deploy?

Node.js, PHP and static builds deploy to Nginx or OpenLiteSpeed servers. Dockerfile and Compose apps, and other language stacks, need a Docker server. Agentic servers running OpenClaw, Hermes, Paperclip or DeepSeek Harness take no additional sites.

Other agents