Claude Code + xCloud

Install one-click apps with Claude Code on xCloud

Installing one-click apps with Claude Code means asking Anthropic's terminal agent to pick an app from the xCloud catalogue, check it against a named server, install it once you approve and report each phase until the app answers.

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

Set up Claude Code All Claude Code guides

YouInstall Uptime Kuma on Frankfurt on a staging hostname. Check it fits first.

oneclickApps_compatibilityread-only

AgentFrankfurt is a Docker server with the stack Uptime Kuma needs, and RAM, CPU and disk are fine on the latest monitoring snapshot. I will install it as uptime on a free staging hostname. Go ahead?

YouYes.

oneclickApps_installneeds approval

AgentInstalling: pre_install done, install done, provisioning... finished. https://uptime-demo.acme.xcloud.site is up. Want the login details?

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 Claude Code to Install one-click apps on xCloud?

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

1
Add the xCloud MCP server
Run this in your terminal, then type /mcp inside Claude Code, pick xcloud and choose Authenticate. The browser opens on the xCloud approval screen, where you tick the teams and choose Read-only or Full access.
Terminal
```
claude mcp add xcloud --transport http https://app.xcloud.host/mcp
```
2
Install the xCloud skills plugin
Optional but recommended. Inside Claude Code, add the xCloud marketplace, install the plugin and reload. The nine skills teach Claude Code which tool to reach for, how to dry-run and confirm, how to poll a long job and how to diagnose a failed deploy.
Terminal
```
/plugin marketplace add xCloudDev/xcloud-agent-skills
/plugin install xcloud@xcloud-agent-skills
/reload-plugins
```
3
No browser? Use an API key
For a headless or CI machine, create a token with the mcp:invoke scope plus the read abilities for the areas it will use (read:servers and read:sites, with read:billing and read:addons for billing and add-on tools) and the matching write: abilities if it should change things in Settings, Developers, API Tokens and pass it as a header. Keep the single quotes: xCloud tokens contain a pipe character.
Terminal
```
claude mcp add xcloud --transport http https://app.xcloud.host/mcp \
  --header 'Authorization: Bearer YOUR_TOKEN'
```

Check it worked

Then ask Claude Code for the job itself, for example:

Prompt

Install Uptime Kuma on my Frankfurt server on a staging hostname. Check it fits first and wait until it is ready.

In practice

How Does One-click apps Work from Claude Code?

You are in a terminal, probably in a project directory, and you have just thought of a tool you would rather not build: an uptime monitor, a blog, a small internal dashboard. You type the request as one line, such as install Uptime Kuma on the Frankfurt server on a staging hostname. Claude Code calls oneclickApps_index to find the app, oneclickApps_show to read the install form, and then oneclickApps_compatibility for the server you named. Those three calls only read, so they run without a prompt, and you see a short summary: the app, what it needs, whether the server fits and whether the resource check was skipped for lack of monitoring data.

What the terminal changes is the pacing. Claude Code restates the app, the server and the address in two or three lines and waits for a plain yes. After that it sends oneclickApps_install with the confirmation flag and an idempotency key, then polls oneclickApps_status and prints a line only when the phase changes, so a six-minute install is four or five lines of output rather than a wall of polling. If a phase fails, it stops and names it, then reads the site's events before it suggests anything. It will not fire the install a second time on a guess.

Because Claude Code lives next to your code, the useful follow-up is about your own project. Once the URL answers, you can ask it to add that address to a health-check script, a README or a deploy workflow in the repository you are in. With the xCloud skills plugin installed, the xcloud:deploy skill supplies the rules around all of this: it asks which server instead of picking one, treats an empty catalogue as an unsynced list, and, for an app that installs only from the dashboard, gives you the path to click rather than trying the call.

Claude Code specific: Login details arrive as plain text in the terminal, so they stay in your scrollback and in whatever session history your setup keeps. Ask for them only when you are ready to paste them into a password manager, then clear the screen. Do not ask Claude Code to write them into a .env file or a script in the repository, because a file in the working directory is easy to commit by accident.

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 Claude Code 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 Claude Code 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 Claude Code 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

Install Uptime Kuma on my Frankfurt server on a staging hostname. Check it fits first and wait until it is ready.

Prompt

Search the one-click catalogue for a self-hosted blog, show me what each result needs, then check the best one against Frankfurt.

Prompt

Give me the login details for the Uptime Kuma app on Frankfurt, then stop and tell me to store them.

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.

Claude Code and One-click apps: Frequently Asked Questions

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

Can Claude Code install a one-click app without me naming a server?

It will not choose silently. Claude Code lists your servers, asks which one, and runs the compatibility check for that server before it installs anything. You approve the app, the server and the address once, and only then does the install start.

Does Claude Code keep polling if I close the terminal during an install?

No. Polling happens inside the session, but the install itself runs on xCloud and continues. Open Claude Code again and ask for the status of the app; it reads the install phase and tells you whether it finished or which phase failed.

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