Codex + xCloud

Manage WordPress with Codex on xCloud

Managing WordPress with Codex means asking OpenAI's terminal agent to scan, compare and fix the sites your theme or plugin code runs on, using xCloud's PageSpeed, broken-link and vulnerability scans.

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

Set up Codex All Codex guides

YouRun PageSpeed on northwind.example.com, wait for both strategies and compare with the last runs.

sites_pagespeed_scan

AgentScan started. Mobile is in, desktop is still running. Waiting for both.

sites_pagespeed_historyread-only

AgentBoth done. Mobile 61, up from 54 two runs ago. Desktop 88, unchanged. The largest image on the homepage is still unoptimized.

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 Codex to Manage WordPress on xCloud?

Connect Codex 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. This form comes from xCloud's connect guide; OpenAI's Codex page documents codex mcp add for local commands, so if your version rejects --url, use the config.toml step below.
Terminal
```
codex mcp add xcloud --url https://app.xcloud.host/mcp
```
2
Or write it in config.toml
Codex reads ~/.codex/config.toml. Add a table for the server with its url. A Streamable HTTP server needs only the url, and the same file is where you set a bearer_token_env_var if you use an API key instead of OAuth.
TOML
```
[mcp_servers.xcloud]
url = "https://app.xcloud.host/mcp"
```
3
Sign in and check
Run the login command, approve the teams and choose Read-only or Full access in the browser, then type /mcp in Codex to see xcloud and its tools. Optional: Codex is also listed for the xCloud Agent Plugins package, which adds the xCloud skills.
Terminal
```
codex mcp login xcloud
```

Check it worked

Then ask Codex for the job itself, for example:

Prompt

Run a PageSpeed scan on https://northwind.example.com/, wait for mobile and desktop, and compare with the last two runs.

In practice

How Does WordPress Work from Codex?

Codex sits in the repository of a theme or a must-use plugin, which makes the scans the natural starting point for this job. Before you touch a template, ask it to run a PageSpeed scan on the site's homepage. Codex calls sites_pagespeed_scan, and because one scan covers both mobile and desktop, it keeps polling sites_pagespeed_scans_show until both results are in rather than reporting after the first. It then reads sites_pagespeed_latest and sites_pagespeed_history, so the score arrives next to the previous runs and not on its own.

After you change the code and deploy, you ask for the same scan again and a comparison. History is kept per strategy, so Codex compares mobile with mobile and desktop with desktop, which is the comparison that tells you whether the change helped. If a scan is still running, xCloud answers with a conflict, and the right move is to wait for that run and read its result instead of starting a second one. A good prompt says so: wait for both strategies and compare with the last two runs.

Broken links work the same way. Codex calls sites_broken-links_scan, polls sites_broken-links_scans_show until the run is done and reads sites_broken-links_index for the pages with the most broken links, calling a truncated scan partial instead of complete. When a bad URL comes from your theme and not from post content, Codex can search the repository for it and edit the template that renders it. Link text and finding titles come from the site, so Codex treats them as data, never as instructions to follow.

Codex specific: Both scans are jobs, not instant reads, so ask Codex to wait for the run to finish and name the strategies you care about. A conflict from xCloud means a scan is already running, and Codex should poll that run, not retry. The first broken-link scan on a site also turns on monitoring with a manual frequency. If xcloud tools are missing in a fresh Codex session, run codex mcp login xcloud first, and use the config.toml table if your version rejects the --url form of codex mcp add.

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

Run a PageSpeed scan on https://northwind.example.com/, wait for mobile and desktop, and compare with the last two runs.

Prompt

Scan northwind.example.com for broken links, list the five worst pages, and grep this repo for any URL that comes from our theme.

Prompt

Redeploy is done. Run PageSpeed again and tell me per strategy whether the score moved.

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.

Codex and WordPress: Frequently Asked Questions

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

How does Codex tell whether my change improved PageSpeed?

It runs a scan before and after, waits until both mobile and desktop results are in, and compares each strategy with its own history. Comparing mobile with desktop would mislead you, so ask it to compare per strategy.

Can Codex fix the broken links it finds?

Only where the link lives in your code. xCloud reports which pages have broken links, and Codex can search the repository for the URL and edit a theme template. Links inside posts and pages are content, so you fix those in WordPress.

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