Cursor + xCloud

Install one-click apps with Cursor on xCloud

Installing one-click apps from Cursor means asking the editor's agent to add a catalogue app, such as an uptime monitor, to the xCloud server that runs the project you have open, after a compatibility check and one approval.

Skill: xcloud:deploy
Toolsets: oneclick-apps, catalog, servers
Free with every xCloud account

Set up Cursor All Cursor guides

YouAdd an uptime monitor next to this project on Frankfurt. Check it fits first.

oneclickApps_compatibilityread-only

AgentUptime Kuma fits Frankfurt: same Docker stack, enough RAM, CPU and disk. I would install it as uptime on a free staging hostname. Go ahead?

YouYes.

oneclickApps_installneeds approval

AgentInstalled. https://uptime-demo.acme.xcloud.site answers. Want me to put that link in the README?

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 Install one-click apps 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

I just deployed this project to Frankfurt. Find an uptime monitor in the xCloud one-click catalogue and check it fits that server.

In practice

How Does One-click apps Work from Cursor?

You are in the editor with a project open, and the agent panel is beside your files. The natural moment to reach for a one-click app is right after a deploy: the site is live and you want something watching it. You type that you want an uptime monitor on the same server as this project. Cursor's agent searches the catalogue, picks the one that matches, reads its install form and runs the compatibility check against the server you name. The answer comes back in the panel as a few lines, and the check never changes anything, so there is nothing to approve yet.

The detail that matters in Cursor is the tool cap. Cursor stops at 40 tools per server, so this connection uses the compact profile at https://app.xcloud.host/mcp?profile=compact: five tools, namely the two searches and three executors split by what a call does. The agent finds the one-click operations through the search tool and runs them through the read executor for the catalogue and compatibility check and the write executor for the install. The work is the same as on any other client, and you give up nothing, but the calls look different in the tool-call panel from what a client with every tool loaded would show.

Editor context is the other difference. Because your repository is open, you can ask the agent to take the finished app's URL and add it where your project needs it, such as a status link in the README or a health-check entry in a config file. The install itself still waits for your yes, the polling runs until the install reaches a terminal phase, and the login details appear once, in the panel, only when you ask. An app that installs only from the dashboard gets a short note with the path to click.

Cursor specific: Under the compact profile, the agent runs the install through a write executor rather than a tool named for the operation, so the approval prompt in Cursor names the executor. Read the arguments in the prompt to confirm the app, the server and the address before you accept. If you keep an API token in .cursor/mcp.json instead of using OAuth, keep that file out of git, because the install is a write call and the token carries write scope.

What xCloud does for one-click apps

xCloud lists the one-click catalogue, checks whether an app fits a given server, installs it once you approve and reports each install phase until it finishes. Afterwards the agent can fetch the login details and stop, start or redeploy the app. A few apps install only from the dashboard, and the agent tells you where to click.

Find the app. The agent searches the catalogue by name or purpose and shows what it found. An empty catalogue means the list has not synced on that environment, so the agent never answers that an app does not exist from an empty list.
Read the install form. The agent reads the app's fields. Fields xCloud generates for you can be left out. For the address you choose a free xCloud staging hostname or your own domain, and a live domain needs the full site name.
Check the server fits. You name the server, or the agent lists yours and asks. The compatibility check covers the server stack, runtime, state, billing and RAM, CPU and disk against the latest monitoring snapshot. If monitoring data is missing the resource check was skipped, and the agent says the result is inconclusive.
Approve and install. The agent restates the app, the server and the address, and asks once. On your yes it sends the install with an explicit confirmation and an idempotency key, so a retried request cannot create a second copy.
Poll the install. The agent polls the install status every five to ten seconds until it is terminal. A failure names its phase: pre_install, install, post_install or provisioning, so you know where it stopped.
Hand over and manage. The agent gives you the URL. It fetches the login details only when you ask, shows them once in the reply and tells you to store them in a password manager. Later it can stop, start, restart or redeploy the app after your approval.

Reference

One-click apps Settings and Limits on xCloud

The facts Cursor works within when it installs one-click apps. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Catalogue	Searchable by name. It holds hundreds of apps, and most run on a Docker server. Public facts such as supported stacks and minimum size come from the catalogue listing
Compatibility check	Per server: stack, runtime, server state, billing and RAM, CPU and disk. monitor_available set to false means the resource check was skipped, not passed
Too-small servers	A server that is too small stays too small. The agent suggests a larger server instead of retrying the install
Stack requirements	An app that needs another stack is refused with a 422 that reads "This app requires a ... server. This server is on the ... stack."
Dashboard-only installs	n8n, Supabase, Nextcloud, Mautic, LibreChat, Open WebUI, Ollama, Umami, WireGuard, phpMyAdmin and Site.pro. The API answers 404 for these eleven; install them from Add site, One-Click Apps in the dashboard
Address	Staging hostname for a free xCloud address, or go live with your own domain. A demo site promoted to a live domain cannot return to the demo address
Idempotency	The install carries an Idempotency-Key, so a retried request cannot create a duplicate site
Install phases	pre_install, install, post_install and provisioning. is_terminal marks the end, and failed_phase says where a failure happened
Credentials	Read on request and shown once in the reply. Some apps have none to read because you create the first admin inside the app
Lifecycle	Stop, start, restart and redeploy run synchronously. Stop takes the app offline and redeploy recreates its containers. Both answer 422 while an install is running or after a failed install
Agentic servers	An OpenClaw, Hermes, Paperclip or DeepSeek Harness server never takes a one-click app

Rules Cursor has to follow

Installing, stopping and redeploying an app stop for your approval; browsing the catalogue and the compatibility check never change anything.
A missing resource reading is reported as inconclusive, never as a pass.
Login details are shown once, only when you ask, and never repeated in a summary or a later message.
For the eleven dashboard-only apps the agent checks that the server fits, then gives you the dashboard path instead of trying the install.
A failed install is not retried blindly: the agent names the failed phase and reads the site's recent events first.

Example prompts

What Can You Ask Cursor to Do for One-click apps?

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

I just deployed this project to Frankfurt. Find an uptime monitor in the xCloud one-click catalogue and check it fits that server.

Prompt

Install Uptime Kuma on Frankfurt on a staging hostname, then add its URL to the status section of the README.

Prompt

The Uptime Kuma install on Frankfurt failed. Which phase failed, and what do the site's recent events say?

Prompt

Which one-click apps are compatible with my Frankfurt server?

Prompt

Search the one-click catalogue for a self-hosted blog and tell me what each result needs from a server.

Prompt

Install Uptime Kuma on the Frankfurt server on a staging hostname, wait until it is ready, then give me the login details.

Prompt

Check whether Immich fits my Amsterdam server before I install it, and tell me if the resource check was inconclusive.

Prompt

I want n8n on my Frankfurt server. Check that the server fits, then tell me where to click to install it.

Prompt

The Uptime Kuma install on the Frankfurt server failed. Which phase failed, and what do the recent events say?

Prompt

Redeploy the Ghost app on blog.example.com, but tell me what a redeploy does before you run it.

Cursor and One-click apps: Frequently Asked Questions

What people ask before they let Cursor install one-click apps through xCloud.

Why does Cursor need the compact URL to install a one-click app?

Cursor stops at 40 tools per server and the full xCloud server advertises far more. The compact profile serves five tools that still reach every operation, including the catalogue, the compatibility check and the install, so nothing about this job is lost.

Can Cursor use my project files when it picks an app?

It can read what is open in the editor to understand what you are building, then search the catalogue for a match. The choice of server, the approval and the install still follow the same steps, and the agent asks you rather than assuming which server to use.

Can an agent install any app in the one-click catalogue?

Most of them. Eleven apps install only from the dashboard: n8n, Supabase, Nextcloud, Mautic, LibreChat, Open WebUI, Ollama, Umami, WireGuard, phpMyAdmin and Site.pro. For those the agent checks that your server fits and points you to Add site, One-Click Apps.

How does the agent know an app will fit my server?

It runs the compatibility check for that server, which covers the stack, runtime, server state, billing and the RAM, CPU and disk readings from the latest monitoring snapshot. If monitoring data is missing, the agent tells you the resource check was inconclusive.

What does a 422 during an app install mean?

Usually that the app needs a different server stack than the one you picked, and the message names both. Pick a server on the required stack. A 422 on stop, start or redeploy means an install is still running or the last install failed.

Where do the login details for a one-click app come from?

The agent can read them from xCloud when you ask and shows them once in the reply. Store them in a password manager. Some apps have no generated login because you create the first administrator inside the app.

Can an agent stop or restart a one-click app?

Yes. Stop, start, restart and redeploy are available, and they run straight away once you approve. Stop takes the app offline and redeploy recreates its containers, so the agent asks before either.

Other agents