How Claude Code handles this
You are in the repository for a content site, and pages that should stay cached for days keep getting rebuilt after a few hours. Instead of opening wp-admin, you type what you want in plain words: keep cached pages for three days on shop, and leave the checkout out of the cache. Claude Code calls list_sites to match the name, then list_modules to see which modules the site has and what settings each one exposes, then get_settings for the cache module so it starts from the real current values.
What comes back is a proposal, not a write. Claude Code shows the current cache expiry in hours, the number it wants instead, and the exclusion it would add, and the Hub tells it to briefly confirm intent before calling update_settings. Once you agree, the call runs and returns the module's settings as stored. Each site checks values against its own schema, so one bad key or value refuses the whole call with a reason and nothing is written, and a setting that belongs to a Pro module is refused on a site without a licence. Credential fields, such as a Cloudflare token or a Redis password, are refused over the Hub and stay in the dashboard.
What differs in Claude Code is where the check lives. Every xSpeed tool has its own name, so a permission rule such as mcp__xspeedhub__get_* can allow the tools whose names start with get_ and leave update_settings and toggle_cache on the prompt. The Hub's request to confirm is guidance to the model, not a lock; your Claude Code prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates. For several sites in one go, the agent passes site: "all" and the Hub tells it to say "this will touch all N sites" first.
Set up Claude Code once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Claude Code 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 Claude Code
Run this once. --scope user makes the server available in every project; leave it off and it applies to the current project only, which is Claude Code's default.
claude mcp add --transport http --scope user xspeedhub https://app.xspeedcache.com/xspeed/mcp
3Sign in with /mcp
Start Claude Code, run /mcp, pick xspeedhub and finish the sign-in in your browser. You approve access on an xSpeed Hub page; there is no token to paste, and Claude Code keeps the credentials it receives and refreshes them.
/mcp
Full Claude Code 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. Claude Code asks before it runs an MCP tool unless a permission rule already allows it, or you work in auto mode, where a classifier reviews actions instead of you, or in bypassPermissions mode, which skips prompts. A rule such as mcp__xspeedhub__get_cache_status allows one tool, and mcp__xspeedhub__get_* allows every read whose name starts with get_. Keep purge_cache, update_settings, toggle_cache and the other write tools on the prompt, because the Hub itself runs a write as soon as your connection allows it.
What do I ask?
Three prompts written for Claude Code. More for this job are below.
Use xSpeed Hub to list the modules on shop, then show me the cache expiry and exclusions and tell me which look wrong for a store that updates once a day.
With xSpeed Hub, set the page cache lifetime to 72 hours on blog only. Read the current value first and tell me the change before you write it.
Ask xSpeed Hub to turn page caching back on for staging, then confirm with get_cache_status that it is on.
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.
01
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.
02
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.
03
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.
04
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.
05
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.
06
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 Claude Code
If you allowed mcp__xspeedhub__* in your permission rules, update_settings and toggle_cache stop prompting, and the Hub's request to confirm intent becomes the only check. Auto mode, where a classifier reviews actions instead of you, and bypassPermissions mode, which asks nothing, skip the prompt too. Allow the read tools by name, such as list_modules and get_settings, and keep the two write tools on the prompt. A server added without the user scope also vanishes in other projects, so a settings change may fail only because you started Claude Code in a different folder.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to list the modules on shop and tell me which ones are off.
Ask xSpeed Hub for the current minify settings on blog.
With xSpeed Hub, turn on HTML minification on blog, then benchmark the cache and tell me if it helped.
Use xSpeed Hub to turn page caching off on staging while I debug, and tell me when it is off.
Using xSpeed Hub, read the gzip settings on shop first, then enable the same options on every site.
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
Keep going
Tune cache settings with other agents
More with Claude Code
Documentation
- How to enable Page Cache
- How to minify CSS and JavaScript
- How to add cache rules and bypasses
- Site MCP tool reference
- How to write prompts for xSpeed Hub
- Claude Code + xSpeed
- Every AI agent that works with xSpeed
From the blog