OpenCode + xCloud

Manage WordPress with OpenCode on xCloud

Managing WordPress with OpenCode means asking the open-source terminal agent which of your xCloud sites need updates, scans or a closer look, then letting it back up, update and check the result after you approve.

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

Set up OpenCode All OpenCode guides

YouWhich WordPress sites have pending updates? Group them by site.

xcloud_sites_wordpress_updatesread-only

Agentnorthwind.example.com: core 0, plugins 3, themes 1. shop.example.com is up to date. I would back Northwind up first and update the plugins. Go ahead?

YouYes, plugins only.

xcloud_sites_wordpress_updateneeds approval

AgentBackup taken and 3 plugins updated. The site events confirm it and northwind.example.com answers 200. The theme update is still pending.

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

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

1
Add the xCloud MCP server
Run this from the project that should use xCloud, or add --global to make it available everywhere. OpenCode writes the entry under mcp.servers in its config (OpenCode v2 no longer accepts server names directly under mcp). Remote servers use OAuth by default, so there is nothing else to fill in; the equivalent hand-written entry is shown below.
Terminal
```
opencode mcp add xcloud --url https://app.xcloud.host/mcp

# the entry it writes to opencode.jsonc
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "xcloud": {
        "type": "remote",
        "url": "https://app.xcloud.host/mcp"
      }
    }
  }
}
```
2
Sign in with OAuth
This opens your browser on the xCloud approval screen, where you tick the teams and choose Read-only or Full access. Inside OpenCode, /mcps does the same: pick xcloud and sign in. Then opencode mcp list should show xcloud as connected.
Terminal
```
opencode mcp auth xcloud
opencode mcp list
```
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 export it as XCLOUD_TOKEN. Setting oauth to false turns off the automatic sign-in, and the {env:XCLOUD_TOKEN} reference keeps the token out of the file. The entry still lives under mcp.servers.
JSON
```
{
  "mcp": {
    "servers": {
      "xcloud": {
        "type": "remote",
        "url": "https://app.xcloud.host/mcp",
        "oauth": false,
        "headers": {
          "Authorization": "Bearer {env:XCLOUD_TOKEN}"
        }
      }
    }
  }
}
```

Check it worked

Then ask OpenCode for the job itself, for example:

Prompt

List my WordPress sites with pending core, plugin or theme updates, grouped by site.

In practice

How Does WordPress Work from OpenCode?

OpenCode normally has a code repository open, and your WordPress fleet is not in it. That changes how you phrase the request. You do not point at a directory; you name a site the way you would to a colleague, such as the Northwind site, and OpenCode finds it by listing your sites and keeping the WordPress ones. Because OpenCode prefixes every MCP tool with the server name, the calls that scroll past in the session read xcloud_sites_wordpress_updates, xcloud_sites_wordpress_plugins and xcloud_sites_wordpress_status, so you can see exactly which read produced each answer.

A fleet question gets a compact answer you can scan in a terminal. Ask which sites have pending core, plugin or theme updates and OpenCode groups the reply by site with counts. Say update the Northwind plugins and it refreshes the cached inventory, then stops for your confirmation before xcloud_sites_wordpress_update runs with backup_before_update set to true. The request returns before the plugins are actually updated, so OpenCode reads the site's events afterwards instead of declaring success on the first response. Scans are lighter: a vulnerability scan and a PageSpeed scan start without a prompt, and a broken-link scan asks first, so you can queue all three from the same session while an update is still running.

OpenCode can switch a server's tools off globally and turn them on for one agent, and that suits this job well. Keep xcloud away from the agent you use for everyday coding, and enable it only for an operations agent whose work is this fleet. If the open project happens to be a theme or plugin you maintain, the same session is where you fix the code and decide whether to apply the matching update. You still never have to leave the terminal to read a magic login link, a WP_DEBUG toggle result or a scan summary.

OpenCode specific: A permission rule written with the pattern xcloud* matches every xCloud tool, including the ones that update plugins and issue magic login links, so scope any rule narrowly or leave the prompts on. A magic login link printed in the terminal also stays in your scrollback, so use it once and do not paste it into a ticket or a shared channel.

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

List my WordPress sites with pending core, plugin or theme updates, grouped by site.

Prompt

Back up the Northwind site, update its plugins, then check that the homepage returns 200.

Prompt

Scan Northwind for broken links and vulnerabilities. Report only and 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.

OpenCode and WordPress: Frequently Asked Questions

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

Does OpenCode need the WordPress code in the project it is running in?

No. xCloud works on the site by name through its API, so the folder OpenCode is open in does not have to be the WordPress install. If the folder is a theme or plugin you maintain, you can ask about the code and the site in the same session.

Why do the WordPress tools show an xcloud_ prefix in OpenCode?

OpenCode adds the server name in front of each MCP tool, so sites_wordpress_updates appears as xcloud_sites_wordpress_updates. Use the same prefix in any permission pattern, and remember that a broad pattern also covers the tools that change a site.

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