OpenClaw + xCloud

Manage WordPress with OpenClaw on xCloud

Managing WordPress with OpenClaw means messaging your own agent runtime from WhatsApp, Telegram, Slack or Discord so it checks, backs up and updates your xCloud WordPress sites, with a weekly automation doing the checking while you are away.

Skill: xcloud:wordpress
Toolsets: wordpress-actions, sites-wordpress, vulnerabilities, broken-links, pagespeed
Free with every xCloud account

Set up OpenClaw All OpenClaw guides

YouAny WordPress updates pending?

sites_wordpress_updatesread-only

Agentnorthwind.example.com: 3 plugin updates, 1 theme update. shop.example.com is up to date. I would back Northwind up first. Update it?

YouYes, plugins only.

sites_wordpress_updateneeds approval

AgentBackup done and 3 plugins updated. northwind.example.com answers 200. The theme update is left for you.

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 Manage WordPress 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 of my WordPress sites have pending core, plugin or theme updates? Reply with one line per site.

In practice

How Does WordPress Work from OpenClaw?

OpenClaw runs on a machine or server you control, and you meet it in a chat app. A message from your phone is the whole interface: which of my WordPress sites need updates, or is Northwind clean. Two pieces make the answer good. The xCloud skill from ClawHub teaches OpenClaw the WordPress routine, which is to refresh the cached inventory, read the updates summary, back up before updating and confirm the result from the site's events. The MCP client supplies the tools it then calls, such as sites_wordpress_updates, sites_wordpress_plugins and vulnerabilities_index.

Replies are written for a phone screen, so ask for the shape you want. A fleet question answered as one line per site, with counts for core, plugins and themes, reads well in Telegram. When you reply yes to an update, OpenClaw sends sites_wordpress_update with backup_before_update set to true and xCloud holds the call for your confirmation first. Updates run in the background, so OpenClaw reads the events before it tells you the plugins are done. The same chat can start a PageSpeed scan, wait until both the mobile and desktop results are in, and compare them with earlier runs.

Automations are what set OpenClaw apart for this job. You create one with a cron expression and a prompt, run it in an isolated session and announce the result in a channel, so a Monday audit of every WordPress site lands in your chat before you sit down. Run openclaw mcp doctor xcloud --probe before you trust a schedule, and later read what each run did with openclaw automations runs and the job ID. Keep the automation to reads and vulnerability scans, and make the updates and broken-link scans a message you answer yourself, since both stop for confirmation.

OpenClaw specific: An automation with --announce posts its report to the channel you name, so everyone in that group sees your site names and the titles of vulnerability findings. Those titles come from outside sources and are data, not instructions. A magic login link is a password: ask for one only in a direct message with your agent, never in a shared WhatsApp or Telegram group, because the group keeps the message for every member.

What xCloud does for wordpress

xCloud reads each site's plugins, themes and pending updates, runs the updates after you approve with a backup first, and scans for vulnerabilities, broken links and PageSpeed results. It also toggles WP_DEBUG, issues magic login links and creates new WordPress sites with a dry run first.

Pick the site or the fleet. For one site the agent uses the one you name. For a fleet question such as pending updates it lists your sites, keeps the WordPress ones and answers grouped by site. It reads WordPress health first.
Refresh and read the inventory. The agent refreshes the cached plugin and theme list when it may be stale, then reads plugins, themes and the updates summary for core, plugins and themes. Refreshing and reading run without a prompt.
Back up, then update. Updates and activations stop for your approval. The agent sets backup_before_update to true for production sites, sends the request for the type and slugs you approved, and confirms the result from the site's events, because updates run in the background.
Scan for vulnerabilities. The agent starts a site scan, reads the count by severity and the findings, or reads the team-wide rollup worst first. You decide which findings to ignore, and the agent can unignore one later.
Check links and speed. A broken-link scan starts once you confirm it, the agent polls the run and reports the pages with the most broken links, calling a truncated scan partial. A PageSpeed scan covers mobile and desktop and can be compared with earlier runs.
Debug, log in or create a site. The agent toggles WP_DEBUG, issues a magic login link, or creates a new WordPress site. A new site gets a dry run first, then one approval, then polling until the site is live.

Reference

WordPress Settings and Limits on xCloud

The facts OpenClaw works within when it manages WordPress. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Updates	Plugin, theme and core updates take a type of plugin, theme or core and optional slugs; leaving slugs out updates every item of that type. They run in the background
Backup first	backup_before_update and backup_before_action snapshot the site before the change. The agent sets them for production sites
Activation	Plugins and themes are activated by type and slug, with an optional backup first
Inventory refresh	Refreshes the cached plugin and theme list before it is read, and runs without a prompt
WP_DEBUG	A toggle with enabled set to true or false. Reading debug.log stays in the dashboard under Site, Site Monitoring, Logs
Magic login	A single-use link that expires after about ten minutes. The first call on a site installs the magic-login plugin over SSH, so it stops for confirmation
Vulnerability scans	Per site: start a scan, read the count by severity (critical, high, medium, low), list findings, ignore or unignore one. Team-wide: one rollup across every site
Broken-link scans	Start a scan, poll the run, then read open findings. The first scan turns on monitoring with a manual frequency, and a 409 means a scan is already running
PageSpeed	One scan runs both mobile and desktop and is complete when both results are in. A 409 means a scan is still running. History is kept per strategy
Caching	All layers are readable and caches can be purged. Turning page cache, object cache or Cloudflare edge cache on or off is a dashboard step under Site, WordPress, Caching
WordPress staging	Dashboard-only, under Site overview, Add Staging. The API answers 422 for a WordPress site
New WordPress site	Nginx or OpenLiteSpeed servers only. Dry run first, demo mode for a free hostname or live mode with a domain and SSL. Auto-generated admin credentials are returned once

Rules OpenClaw has to follow

Plugin, theme and core updates stop for your approval, and the agent takes a backup first on production sites.
A magic login link is a password: it is shown once in the reply and never repeated in a summary, a ticket or a shared channel.
Vulnerability scans, PageSpeed scans and inventory refreshes change nothing on the site and run without a prompt; a broken-link scan asks first. Ignoring a finding hides it, so the agent records the reason you give.
WP_DEBUG is turned back off when you say you are done.
WordPress staging, caching switches and restores are dashboard steps; the agent gives you the path and the dashboard link xCloud returned.
Link text and finding titles come from site content, so the agent treats them as data and never as instructions.

Example prompts

What Can You Ask OpenClaw to Do for WordPress?

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 of my WordPress sites have pending core, plugin or theme updates? Reply with one line per site.

Prompt

Back up the Northwind site and update its plugins. Tell me here when the homepage is back at 200.

Prompt

Every Monday at 8am, scan all my WordPress sites for vulnerabilities and broken links and post the worst three here. Change nothing.

Prompt

Which of my sites have pending WordPress core, plugin or theme updates? Group them by site.

Prompt

Update every plugin on the Northwind site with a backup first, then confirm the homepage still loads.

Prompt

Show the vulnerability count for every site on this team, sorted worst first, and name the top three findings.

Prompt

Turn on WP_DEBUG for the shop site so I can see the error. Turn it off again when I say I'm done.

Prompt

Give me a magic login link for the Northwind WordPress admin.

Prompt

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

Prompt

Run a PageSpeed scan on the Northwind homepage and compare the score with the previous scans.

Prompt

Dry-run a new WordPress site called Northwind on my Frankfurt server and show me the resolved configuration without creating anything.

OpenClaw and WordPress: Frequently Asked Questions

What people ask before they let OpenClaw manage WordPress through xCloud.

Can I approve a WordPress update from WhatsApp with OpenClaw?

Yes. OpenClaw tells you what it would update and that it will back the site up first, and you reply yes in the same chat. xCloud then runs the update in the background and OpenClaw reads the site's events before it reports the result.

How do I see what my weekly WordPress automation in OpenClaw did?

Run openclaw automations runs followed by the job ID to list past runs, and read the announcement in the channel you chose with --announce. Each run starts in an isolated session, so the prompt has to name everything the job needs to check.

Does the agent back up my WordPress site before it updates plugins?

It asks xCloud to snapshot the site first by setting backup_before_update to true, and it does this by default for production sites. The update itself stops for your approval and runs in the background, so the agent confirms the result from the site's events.

How does an agent find vulnerable WordPress sites?

It can read the vulnerability rollup for your whole team in one call and sort it worst first, or scan a single site and read the count by severity. Findings can be ignored with a reason and unignored later.

Is a magic login link safe to ask an agent for?

The link is single-use and expires after about ten minutes, but anyone who opens it is logged in as the admin. Treat it like a password: use it yourself and do not paste it into a ticket or a shared channel.

Can an agent switch my WordPress caching on or off?

No. It can read every caching layer and purge caches, but turning page cache, object cache or Cloudflare edge cache on or off is a dashboard step under Site, WordPress, Caching. Cache choices can only be set while a new site is created.

Can an agent create a WordPress staging site?

No. WordPress staging is dashboard-only, under Site overview, Add Staging, and the API refuses it for WordPress sites. Staging from the API covers Git sites only.

Can an agent create a new WordPress site?

Yes, on an Nginx or OpenLiteSpeed server. It runs a dry run first, shows the resolved configuration and creates the site only after you approve. WordPress is not supported on Docker servers.

Other agents