Tune WordPress cache settings with OpenCode

Tuning cache settings with OpenCode means asking it, in the terminal, to read the xSpeed settings of a WordPress site and write a change through xSpeed Hub, with your permission rules deciding which calls run unasked.

list_sitesget_cache_statuslist_modulesget_settingsupdate_settingstoggle_cacherun_benchmark

Last updated: October 2026

Example session · OpenCode

You: My build already minifies CSS. Using xSpeed Hub, what is xSpeed doing to it on shop?

get_settings(site: shop, module: minify) read-only
→ minify_css on, combine_css on, minify_js on

OpenCode: Minify CSS is redundant but harmless. Combine CSS files merges your separate stylesheets into one, which can undo how your build splits them. I would turn off Combine CSS files only. Apply it to shop?

You: Yes, only that one.

update_settings(site: shop, module: minify, values: { combine_css: false }) changes site
→ stored, combine_css off, other minify options unchanged

OpenCode: Done. Purge the assets cache so the old combined file is not served.

How OpenCode handles this

You are in OpenCode in a theme repository, and the stylesheet your build produces is already minified, so you suspect xSpeed is doing the same work twice or combining files that you serve separately on purpose. You ask it to look at the minify settings on shop. OpenCode calls list_sites, then list_modules to find the minify module, then get_settings for it, and reads which of minify CSS, minify JavaScript, and combining files are on.

What comes back is a comparison with your build: your theme already ships minified CSS, so xSpeed can keep minifying JavaScript and leave Combine CSS files off. The Hub tells the agent to briefly confirm intent before update_settings, so OpenCode states the change and waits. After your yes it calls update_settings and returns the stored values. If any key or value is wrong, the whole call is refused and nothing is stored, Pro-only modules are refused on an unlicensed site, and credential fields are refused over the Hub.

What differs in OpenCode is that most permissions default to allow, so with no rule of yours a Hub write runs without a prompt. OpenCode checks MCP tools under their prefixed name, such as xspeedhub_update_settings. Add a rule that sets xspeedhub_* to ask, then allow rules for xspeedhub_get_* and xspeedhub_list_*, because the last matching rule wins. Then a settings change always stops at a prompt in your terminal. For a session that cannot change anything, set the write tools to deny. The Hub runs a write as soon as the connection allows it, so these rules are where you decide.

Set up OpenCode once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the OpenCode guide.

1Put your sites in xSpeed Hub

Sign in at app.xspeedcache.com with Google or email; the Hub is free and has no site cap. Then connect each WordPress site from its own dashboard: click Connect Hub in the xSpeed Cache top bar, then Connect via xSpeed Hub. Each site needs the free xSpeed Cache plugin.

2Add xSpeed Hub to your config

Put this block in your global config, or in opencode.json at a project root to scope it to that project. OpenCode reads both JSON and JSONC. No other field is needed: when the Hub answers 401, OpenCode starts the OAuth flow and registers itself through dynamic client registration.

~/.config/opencode/opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xspeedhub": {
      "type": "remote",
      "url": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}

3Sign in with opencode mcp auth

Run this once. It opens a browser page on xSpeed Hub where you sign in and approve access. There is no token to paste; OpenCode stores the credentials it receives. Run opencode mcp list to see the server and its auth status, and opencode mcp debug xspeedhub if the connection fails.

Terminal

opencode mcp auth xspeedhub

1 / 3

Full OpenCode setup, sign-in options and FAQ

Before you send a prompt that changes something

Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. OpenCode checks MCP tools against its permission rules under the prefixed name, such as xspeedhub_purge_cache, and most permissions default to allow. With no rule of yours in place, a Hub write tool runs without a prompt. Add rules to change that: "xspeedhub_*": "ask" first, then "xspeedhub_get_*": "allow" and "xspeedhub_list_*": "allow", because the last matching rule wins. A deny rule holds even under opencode --auto, which approves everything that is not denied. The Hub itself has no confirmation step, so these rules and read-only access are the gates. For read-only access, send the connection token with Read-only everywhere on, or sign in as a Viewer member.

What do I ask?

Three prompts written for OpenCode. More for this job are below.

Prompt for OpenCode

With xSpeed Hub, check the minify settings on shop against my theme build, which already minifies CSS, and tell me what is redundant.

Prompt for OpenCode

Use xSpeed Hub to turn off combining CSS files on shop and keep JavaScript minify on. Show me the setting before and after.

Prompt for OpenCode

Ask xSpeed Hub for the browser cache settings on blog and tell me whether they match the cache expiry.

What happens, step by step

Every xSpeed feature is a module with its own settings. Through xSpeed Hub an agent can list the modules a site has, read one module's settings, change them with a checked update, and turn page caching on or off. The site validates every write against the module's own schema, so a wrong key or value is refused with a reason instead of being quietly ignored.

List the modules

list_modules returns every Free and Pro module available on one site, with its settings schema and status. It tells the agent which module slugs exist, such as minify or gzip, and what each setting accepts.

Read the current settings

get_settings takes a module slug and returns its settings. Credential fields come back masked, so an agent cannot read a stored API token or password back in plain text.

Change them

update_settings takes the module and a values object of setting keys. The site checks the whole object first. If any key is unknown, any value is outside the schema, or a field is pinned by a constant in wp-config.php, it refuses the write, writes nothing and says which keys and why, sometimes with a "did you mean" hint.

Turn page caching on or off

Page caching has its own tool, toggle_cache, because it installs or removes the cache drop-in and the WP_CACHE constant. Asking update_settings to set cache_enabled does not work and is refused. If another caching plugin owns the drop-in, the site declines to enable xSpeed and returns blocked: true with the reason.

Check the effect

The result of a settings write is the stored settings. A module can add a warning when a setting is saved but has no effect on this server, for example Brotli on a server without the module for it, and the agent should pass that on. run_benchmark then times cached against uncached to see whether the change helped.

Apply to many sites only after reading one

update_settings and toggle_cache accept site: "all" or a list of handles. Each site validates against its own schema and answers in its own row, so a module missing on one site fails that row and the others still apply. Read one site first, then apply.

Reference

Discover	list_modules (read): Free and Pro modules, settings schema, status, per site
Read settings	get_settings (read): argument module; credential fields masked
Change settings	update_settings (write): arguments module and values; validated by the site
Bad input	The whole write is refused and nothing is written; the error names the keys and reasons
Page cache on or off	toggle_cache (write): argument enabled; cache_enabled in update_settings is refused
Blocked by another plugin	toggle_cache returns blocked: true with blocked_reason when another plugin owns the cache drop-in
Every site at once	update_settings and toggle_cache accept site: "all" or a list of handles, one result per site
Pro modules	A Pro module on a site without an active licence cannot be read or written; the site refuses
Credential fields	Refused by default over MCP; set them in the xSpeed dashboard, not through the agent
Read-only connection	The connection token with Read-only everywhere on, or a Viewer member's sign-in: update_settings and toggle_cache are refused; list_modules and get_settings still work. An OAuth sign-in gets the scopes the client asks for, read and write by default, clamped to the member's role
Confirmation	None on the Hub; the Hub tells the agent to briefly confirm intent for these two, and your client's prompt is the gate

Rules worth keeping

Read before you write. Ask for list_modules and get_settings first, so the agent changes real keys with valid values instead of guessing.
update_settings and toggle_cache change how a live site behaves. They run as soon as your connection allows writes. The Hub tells the agent to briefly confirm intent first, which is guidance to the agent, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates. The switch does not limit an OAuth sign-in.
For site: "all", the Hub tells the agent to confirm once with "this will touch all N sites", then make one call. The result is per site, and some sites failing is a partial result to report, not a blanket success or failure.
Do not ask an agent to set credentials such as a Cloudflare token or Redis password. The site refuses those writes by default, and they belong in the xSpeed dashboard.
If a settings result says a value is saved but inactive on this server, relay that. Do not tell the user the feature is enabled.

Good to know with OpenCode

OpenCode starts from permissive defaults, so until you add an ask or deny rule for xspeedhub_ tools, update_settings and toggle_cache can run on the model's say-so. Order matters because the last matching rule wins: put the catch-all ask rule first and the allow rules for the reads after it. A deny rule holds even under opencode --auto, which approves everything that is not denied, so deny any tool you never want to run.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Use xSpeed Hub to list the modules on shop and tell me which ones are off.

Prompt

Ask xSpeed Hub for the current minify settings on blog.

Prompt

With xSpeed Hub, turn on HTML minification on blog, then benchmark the cache and tell me if it helped.

Prompt

Use xSpeed Hub to turn page caching off on staging while I debug, and tell me when it is off.

Prompt

Using xSpeed Hub, read the gzip settings on shop first, then enable the same options on every site.

Prompt

Use xSpeed Hub to set the page cache lifespan on docs to 30 days, and if the site refuses it, tell me why.

Frequently asked questions

Set the write tools, such as xspeedhub_update_settings and xspeedhub_toggle_cache, to deny in your permission configuration, or connect with a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) so the Hub refuses them. The second method works even if a permission rule is wrong, because the refusal happens at the Hub.

Yes, because it can read your repository and the live site settings in the same session. It can see that your build already minifies CSS and compare that with the minify module, then propose one setting change. You still approve the write.

It calls list_modules for the site, which returns every available module with its settings schema and status, then get_settings for the one module it wants to change. The schema says which keys exist and what values each accepts.

The site refuses the whole update and writes nothing. The error names the keys it rejected and why, such as an unknown key, a value outside the allowed range, or a field fixed by a constant in wp-config.php, and it can suggest the nearest valid key.

Use toggle_cache with enabled set to true or false. It installs or removes the cache drop-in and the WP_CACHE constant. Setting cache_enabled through update_settings does not work. If another caching plugin already owns the drop-in, the site will not enable xSpeed and says why.

Yes. update_settings and toggle_cache accept site: "all", and the Hub runs the sites one after another with a one-second pause and returns a result per site. Each site checks the values against its own schema, so a site that lacks the module fails its own row while the others apply.

Not by default. Writing credential fields over MCP is off unless the site owner allows it, and the site refuses the write and names the fields. Set credentials in the xSpeed dashboard. Credential values also come back masked when an agent reads settings.

Tune cache settings, from OpenCode.

xSpeed Hub is free and has no site cap. Connect your sites once and ask from the agent you already use.

Open xSpeed Hub OpenCode setup

Tune WordPress cache settings with OpenCode

How OpenCode handles this

Set up OpenCode once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Tune cache settings, from OpenCode.