OpenClaw + xCloud

Speed up a slow site with OpenClaw on xCloud

Speeding up a slow site with OpenClaw means sending a message to the agent runtime you already host, and letting its xCloud performance skill and MCP tools read the site's measurements and name the cause in the same chat.

Skill: xcloud:performance
Toolsets: pagespeed, sites, servers, broken-links
Free with every xCloud account

Set up OpenClaw All OpenClaw guides

Youshop.example.com feels slow tonight. Four lines please.

sites_cacheSettingsread-only

servers_servicesread-only

AgentObject cache reads as on, but the Redis service is stopped on the server, and page cache is on. That is the likely cause. Restarting a service is a separate step, so I will not do it unasked. Want me to?

YouYes, restart it.

servers_services_restart

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 Speed up a slow site 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

shop.example.com feels slow tonight. Check the server and the caches and reply in four lines.

In practice

How Does Performance Work from OpenClaw?

OpenClaw lives on your own machine or server, and you reach it from the chat app you keep open anyway: WhatsApp, Telegram, Slack or Discord. When a customer writes that the shop is slow, you do not have to find a laptop. You message OpenClaw, shop.example.com feels slow tonight, check the server and the caches, and reply in four lines. The xcloud skill from ClawHub recognises that as a performance question and keeps it apart from a site that errors, which would go to troubleshooting. Through the MCP client it then reads the site and server status, the monitoring history, sites_cacheSettings, sites_pagespeed_latest, the services on the server and the site's PHP version.

The answer arrives as a chat message, so it is short. Expect the cause and its numbers, for example a disk close to full or an object cache that reads as on next to a Redis service that is stopped. Expect, too, a plain statement about what OpenClaw cannot do. It can read whether page cache, Redis object cache or Cloudflare edge cache is on, and it can purge them after you agree, but enabling a layer is a dashboard step under Site, WordPress, Caching, and changing one site's PHP version is under Site, Site Settings. Both come with the site's dashboard link, which you can open from the same chat on your phone.

Two OpenClaw features shape this job. Automations let you schedule a Monday-morning performance digest that runs in an isolated session and announces the result in a channel, so slowness is noticed before a customer notices it. And the skill and the MCP connection are separate: the skill carries the judgement, such as reading the cache settings before saying anything about caching, while the MCP client carries the tools. Run openclaw mcp doctor xcloud --probe once if a reply says the tools are missing, because a saved server entry proves nothing until the probe passes.

OpenClaw specific: The xcloud skill without the MCP connection falls back to a GET-only REST wrapper. That is enough to read the measurements, but it cannot start a PageSpeed scan or purge a cache, so a chat reply may stop at a finding and tell you to connect MCP. Scheduled automations have nobody watching, so keep a performance digest to reads, and send the purge or restart as a message you can approve.

What xCloud does for performance

xCloud reads the site's and the server's CPU, RAM and disk samples, which cache layers are on, the latest PageSpeed result, traffic in the access log, service health and the site's PHP version. The agent names the cause from that data, then hands you the switches that only the dashboard can flip.

Resolve the site and its server. The agent looks up the site and the server it runs on, because the answer often comes from both. A slow site is frequently slow because a neighbour on the same server is.
Check status and monitoring history. A site that is mid-deploy or failed explains slowness without any measurement. Otherwise the agent reads the site's and the server's samples, and a 24-hour or 7-day series to tell whether the slowdown is new. Disk comes early: a nearly full disk slows everything, the database first.
Read the cache layers. The agent reads the cache settings before saying anything about caching: whether page cache, Redis or Object Cache Pro object cache and Cloudflare edge cache are on, and which server stack the site runs. It never reports that no cache configuration is readable without calling it.
Read PageSpeed and traffic. The latest completed PageSpeed run is free to read. A new scan is worth starting only when there is no result or the site changed since, and the agent tells you it is spending a scan. The access log shows spikes, a crawl or one client hammering a path.
Check services and PHP. The agent checks that PHP, the web server, Redis and the database are running, and reads the site's PHP version and pending updates. A stopped Redis next to an object cache that reads as on is a found answer.
Name the cause and hand off. You get the most likely cause with its numbers. The fix is either something the agent can do, such as a purge after you agree, or a dashboard switch it names with the path and the site's dashboard link. If every number looks normal, it says so instead of inventing a cause.

Reference

Performance Settings and Limits on xCloud

The facts OpenClaw works within when it speeds up a slow site. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Monitoring history	Site and server CPU, RAM and disk samples as a 24-hour or 7-day series. History is not available on the free plan, and the agent says that is a plan limit rather than reporting no data
Cache state	Read through sites.cacheSettings: page cache, object cache (Redis, Object Cache Pro) and Cloudflare edge cache. It returns settings only, never cache contents
Enabling a cache layer	Dashboard-only: Site, WordPress, Caching. The API reads the layers and purges them, and cannot switch one on for an existing site
Page cache details	Cache duration, URL and cookie exclusions and ignored query parameters are dashboard-only and are not returned by the cache settings read
PageSpeed	The latest mobile and desktop results and the history are read for free. One scan runs both strategies
Scan conflicts	A 409 while a scan is running means it is still pending or scanning. The agent polls it instead of starting another, and it is not a cooldown
Cache purge	Purging runs without a confirmation stop but throws away a warm cache, so the agent asks first on a live site and reports each layer as queued or skipped
Traffic	The access log shows spikes and bots. It is read over SSH, so the agent asks for a bounded window
PHP version	Read from the site's status. Changing one site's PHP version is a dashboard step: Site, Site Settings
Server PHP default	Changing the server default PHP changes only the command-line php and the version new sites get. It does not move any existing site
Broken links	A broken-link scan on a WordPress site returns findings grouped by source page, and a truncated scan is reported as partial

Rules OpenClaw has to follow

The agent diagnoses from measurements, not guesses, and it calls the cache settings read before it says anything about caching.
It never offers to turn on Redis or any other cache layer itself. Enabling a layer is a dashboard step, and the agent gives you the path and the dashboard link.
It never presents a change of server PHP default as a substitute for changing one site's PHP version.
A cache purge on a live site, a new PageSpeed scan and any server-level PHP change are announced first. Server-level changes also need your explicit yes.
A site that errors rather than loads slowly goes to troubleshooting, and a failed deploy goes to deploy.

Example prompts

What Can You Ask OpenClaw to Do for Performance?

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

shop.example.com feels slow tonight. Check the server and the caches and reply in four lines.

Prompt

Is Redis running on the server behind shop.example.com, and does the site say object cache is on?

Prompt

Every Monday at 7am, read the cache settings and latest PageSpeed result for shop.example.com and post what changed here. Change nothing.

Prompt

Why is shop.example.com slow? Check the cache, the server load and the latest PageSpeed result.

Prompt

Is Redis object cache on for the shop site? If it is off, tell me where to switch it on.

Prompt

Show CPU, RAM and disk for the shop site over the last 24 hours and tell me whether the slowdown is new.

Prompt

Run a PageSpeed scan on the shop site and compare the score with the previous scans.

Prompt

Look at the access log of the shop site for a traffic spike or a bot hammering one path.

Prompt

Which PHP version is the blog site running, and are there pending updates I should apply?

Prompt

Purge all caches on the shop site.

Prompt

Scan the shop site for broken links and list the pages with the most.

OpenClaw and Performance: Frequently Asked Questions

What people ask before they let OpenClaw speed up a slow site through xCloud.

Can OpenClaw run a weekly speed check for my site?

Yes. Create an automation with a cron expression and a prompt that reads the latest PageSpeed result, the cache settings and the server's disk, and announce the result in your chat channel. Keep it to reads, since a scan spends a PageSpeed run and a purge empties a warm cache.

Why does OpenClaw say it cannot turn on caching?

Enabling page cache, Redis object cache or Cloudflare edge cache for an existing site is dashboard-only. OpenClaw can read which layers are on and purge them, so it gives you the path, Site, WordPress, Caching, and the site's dashboard link.

Can the agent turn on caching for my slow site?

No. It can read which cache layers are on and purge them, but switching page cache, Redis object cache or Cloudflare edge cache on for an existing site is a dashboard step under Site, WordPress, Caching. The agent tells you the path and gives you the site's dashboard link.

What does a 409 mean when the agent starts a PageSpeed scan?

It means a scan for that site is still pending or running. The agent polls the existing scan instead of starting another, and it is not a cooldown period. A new scan is only worth starting when there is no recent result or the site has changed.

Will changing the server's PHP default speed up my site?

No. The server default changes only the command-line php and the version new sites get, and it does not move any existing site. The PHP version of one site is changed in the dashboard under Site, Site Settings.

Why does the agent say monitoring history is unavailable?

Monitoring history is a paid-plan feature, so on the free plan the request is refused as a plan limit. The agent reports it that way rather than saying there is no data, and it falls back to the samples and measurements the plan does include.

Does purging the cache ask for my confirmation?

xCloud itself runs a purge without a confirmation stop, because it is a routine action. The agent still asks you first on a live site, since a purge throws away a warm cache and the next visitors wait while it rebuilds.

Other agents