OpenClaw + xCloud

Install one-click apps with OpenClaw on xCloud

Installing one-click apps with OpenClaw means sending a message from WhatsApp, Telegram, Slack or Discord to the agent runtime you host yourself, and having it search the xCloud catalogue, check a server, install the app once you say yes and tell you the address.

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

Set up OpenClaw All OpenClaw guides

YouPut Ghost on Frankfurt, staging hostname.

oneclickApps_compatibilityread-only

AgentGhost fits Frankfurt: stack, runtime and billing pass. The resource check is inconclusive because there is no recent monitoring reading. Install on a staging hostname?

YouYes.

oneclickApps_installneeds approval

AgentInstalled. Ghost is ready on its staging hostname. Say the word if you 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 OpenClaw to Install one-click apps on xCloud?

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

1
Install the xCloud skill from ClawHub
This installs the nine xCloud skills into the active workspace skills folder. Add --global to install them into ~/.openclaw/skills for every local agent. The clawhub CLI installs the same listing with clawhub install xcloud.
Terminal
```
openclaw skills install @asif2bd/xcloud
```
2
Add the xCloud MCP server and sign in
Run these on the installation that owns the connector. The --auth oauth flag matters: openclaw mcp login only runs for HTTP servers saved with OAuth, so without it the login is refused. The login prints an authorization URL, and OpenClaw normally captures the redirect on a loopback address and saves the credentials; Settings, MCP, Sign in in the Control UI does the same. On the xCloud approval screen tick the teams and choose Read-only or Full access.
Terminal
```
openclaw mcp add xcloud \
  --url https://app.xcloud.host/mcp \
  --transport streamable-http \
  --auth oauth
openclaw mcp login xcloud
```
3
Check the skill and the connection
The first command lists the skills that are eligible to run in this environment, and xcloud should be among them. The second opens a live connection and reports the tools the server offers. A saved server entry proves nothing until the probe passes. Then ask who am I on xCloud.
Terminal
```
openclaw skills list --eligible
openclaw mcp doctor xcloud --probe
```
✓
Check it worked
Then ask OpenClaw for the job itself, for example:
Prompt
```
Which one-click apps fit my Frankfurt server? Reply in a short list.
```

In practice

How Does One-click apps Work from OpenClaw?

OpenClaw has two halves for xCloud, and the install job uses both. The xcloud skill from ClawHub carries the sequence: read the install form, run the compatibility check before anything else, and restate the app, server and address before it asks you once. The MCP client carries the tools, from oneclickApps_index to oneclickApps_install. Run openclaw mcp doctor xcloud --probe before you rely on it. If only the skill is present, OpenClaw falls back to a GET-only REST wrapper: it can browse the catalogue, run the compatibility check and read install progress, but it cannot send the install, and it will tell you to connect MCP.

In a chat the exchange is short and mobile-friendly. You write: put Ghost on my Frankfurt server with a staging hostname. OpenClaw replies with the compatibility verdict in a couple of lines, for example that the stack matches and the resource check was inconclusive because the server has no fresh monitoring reading, then asks for your go-ahead. Your yes sends the install with its idempotency key, so a message retried over a flaky mobile connection cannot create a duplicate site. OpenClaw polls the status and posts to the same chat when the install is done or when it fails, naming the failed phase. Login details come only when you ask and appear once in that reply.

Automations are where OpenClaw differs from an editor agent, and where you should hold back. An automation runs in an isolated session, announces its result in a channel and has nobody to approve a change. Use it for read-only jobs, such as a Monday message that lists your servers and how close each is to its limits before you plan another app, and keep installs, stops and redeploys for a live conversation where your reply is the approval.

OpenClaw specific: Check where the app will land. An OpenClaw, Hermes, Paperclip or DeepSeek Harness server never takes a one-click app, so if the server where OpenClaw itself runs was provisioned on xCloud as one of those, name a different server for the install. Also run the mcp commands on the installation that owns the connector: an OpenClaw gateway on another host will not see the xcloud server until it reloads.

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 OpenClaw 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 OpenClaw 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 OpenClaw 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

Which one-click apps fit my Frankfurt server? Reply in a short list.

Prompt

Put Ghost on Frankfurt with a staging hostname. Check the fit first, ask me once, then message me the URL.

Prompt

Every Monday at 8am, list my servers by how full they are so I know where another app would fit. Change nothing.

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.

OpenClaw and One-click apps: Frequently Asked Questions

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

Can OpenClaw install a one-click app with only the xCloud skill?

No. Without the MCP connection the skill falls back to a GET-only REST wrapper. That can browse the catalogue, run the compatibility check and read install progress, but sending the install needs a connected MCP tool and your approval.

Can I install a one-click app on the server that runs OpenClaw?

Not if that server is an OpenClaw server provisioned on xCloud. Agentic servers, which include OpenClaw, Hermes, Paperclip and DeepSeek Harness, never take a one-click app. Ask OpenClaw to check another server instead.

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