Cursor + xCloud

Manage Your Hosting from Cursor with xCloud

Cursor is an AI code editor with an agent that can use external tools through the Model Context Protocol. Connected to xCloud, it deploys the project you have open, checks servers and sites, and fixes failed builds without you leaving the editor.

One entry in mcp.json
Compact URL stays under the 40-tool cap
Free with every xCloud account

Connect Cursor Every agent

YouDeploy this project to my Frankfurt server on a staging hostname.

git_detectread-only

AgentNode.js app on main, build npm run build, start npm start. Dry run passed. Create the staging site on Frankfurt?

YouYes.

servers_sites_git_createneeds approval

AgentDeployed. SSL issued and the staging URL answers 200.

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 I Connect Cursor to xCloud?

Point Cursor at the xCloud MCP server, approve access in your browser, then ask. The whole thing takes a couple of minutes. The xCloud Agent Skills are an optional layer on top of that connection: they teach the agent the workflows, they do not replace it.

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
Cursor signs you in with OAuth in the browser. If you prefer a key, add a headers entry to the same mcp.json block with an Authorization Bearer token that carries the mcp:invoke scope and the read or write abilities it needs, and keep the token out of git.
Prompt
```
Who am I on xCloud?
```

Three surfaces

Which Way Should I Connect Cursor to xCloud?

The MCP server exposes one tool per customer-facing xCloud operation and leaves out eleven internal ones that only the Public API carries; the skills add workflow know-how on top of an MCP connection and, on their own, only read access. All three are free with every account and differ in what you set up and what holds the credentials.

	xCloud MCP server	xCloud Agent Skills	Public API
Terminal needed	No (recommended for Cursor)	Yes for the plugin or ClawHub install	Yes
Authentication	OAuth sign-in, or an API key with mcp:invoke plus read or write abilities (recommended for Cursor)	The MCP connection, or a read-scoped API token	API token with scoped abilities
What it adds	One tool per customer-facing xCloud operation (188 today) (recommended for Cursor)	Workflow know-how: routing, dry run, confirm, poll, diagnose	Raw REST for your own code
Changes to your infrastructure	Yes, after confirmation (recommended for Cursor)	Only through a connected MCP tool, after confirmation	Yes, with write scopes
Best for	Most people; every MCP client (recommended for Cursor)	Agents that run shell commands and read skills	CI jobs, dashboards and long-running loops

Background

What Is Cursor?

Cursor is an AI code editor. It looks like a familiar editor, with an agent beside your files that can read the project, edit code, run commands and work through multi-step tasks. You choose how much it does on its own and what it must ask about.

Cursor can call outside tools through the Model Context Protocol. You list MCP servers in a JSON file, either ~/.cursor/mcp.json for every project or .cursor/mcp.json for one, and Cursor supports OAuth for servers that need a sign-in. xCloud runs a remote MCP server at https://app.xcloud.host/mcp that fits that format.

Because the agent already has your repository open, a deploy does not need a trip to a dashboard. It reads the project, hands the details to xCloud, shows you the plan and waits for your approval before it creates anything.

Why Cursor with xCloud?

Deploy the project you have open

The agent already sees your repository, branch and build files. Ask it to deploy and it passes them to xCloud, dry-runs the site and asks once before creating anything.

Built for the 40-tool cap

The compact profile gives Cursor five tools: two searches and three executors split by what a call does. It stays under the cap and still reaches every customer-facing xCloud operation.

Skills package for Cursor too

Cursor is listed for the portable Agent Plugins package, which carries the xCloud skills and the MCP connection in one install. The skills add the judgement about dry runs, confirmation and diagnosis.

Guides

What Can Cursor Do on xCloud?

One guide per hosting job, each with the Cursor setup, the xCloud tools involved, a settings reference, example prompts and the limits that apply.

Example prompts

What Can You Ask Cursor to Do on xCloud?

Type these as written and swap in your own 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 repository to my Frankfurt server and show me the dry run before you create anything.

Prompt

The last deploy of this project failed. Find the cause in the xCloud logs, fix the build command and retry.

Prompt

Is example.com up, is SSL healthy and is the PHP version current?

Prompt

Back up shop.example.com, then update its plugins and check the homepage still loads.

Prompt

Add a cron job on my staging server that runs php artisan schedule:run every minute.

Good to know

Cursor stops at 40 tools per server. The full xCloud server has 188 operations plus two search tools, so use ?profile=compact. Toolsets alone rarely fit: the servers toolset is 61 tools and sites is 60.
A project .cursor/mcp.json travels with the repository. If you use an API token instead of OAuth, keep it out of any file you commit.
Cursor's docs point to the Customize page for managing MCP servers. If the menu names differ in your version, the mcp.json file works the same way.

More prompts, grouped by job: What you can ask xCloud MCP to do.

Cursor and xCloud: Frequently Asked Questions

Short answers about connecting Cursor, what it may change and what it costs.

How do I connect Cursor to xCloud?

Add an xcloud entry with the url https://app.xcloud.host/mcp?profile=compact under mcpServers in ~/.cursor/mcp.json, or in .cursor/mcp.json inside a project. Click the login prompt Cursor shows, approve the access in your browser and ask who am I on xCloud.

Why does Cursor need the compact xCloud URL?

Cursor stops at 40 tools per MCP server, and the full xCloud server advertises one tool per customer-facing operation. The compact profile at https://app.xcloud.host/mcp?profile=compact serves five tools, so Cursor loads them all and can still reach every operation through the search and executor tools.

Where does Cursor keep the MCP configuration?

In two places. ~/.cursor/mcp.json applies to every project, and .cursor/mcp.json inside a project applies to that project only. Both use an mcpServers object, and a remote server needs a url and optionally headers.

Does Cursor need an xCloud API key?

Not when you sign in with OAuth. If you prefer a key, add a headers entry to the xcloud block with an Authorization Bearer token that carries the mcp:invoke scope and the read or write abilities it needs. xCloud tokens contain a pipe character, so keep the value exactly as shown in the dashboard.

Can Cursor change my servers without asking?

Not for the operations xCloud gates. Reads and routine actions such as backups, cache purges, PageSpeed and vulnerability scans run without a prompt. Creating a site or server, deploying, updating plugins, rebooting, deleting or buying is refused by xCloud unless the call carries an explicit confirmation, so Cursor asks you first.

Can I install the xCloud skills in Cursor?

Yes. Cursor is listed for the portable Agent Plugins package, which bundles the xCloud skills and the MCP connection and comes from the GitHub releases of xcloud-agent-skills. The MCP connection alone already gives Cursor every xCloud tool.

Can Cursor work across several xCloud teams?

Yes. On the approval screen you tick every team the connection may act on, and you name the team in your request. A site on a team you did not tick comes back as not found, so reconnect and tick it.

Is it free to use Cursor with xCloud?

The xCloud side is free: the MCP server, the skills and the Public API are included with every xCloud account, including the free plan. Cursor itself is billed by Cursor under your Cursor plan.

Other agents