Manage every WordPress site at once with Claude Code

Managing every WordPress site at once with Claude Code means asking, from the terminal you ship from, for one xSpeed Hub call that purges, warms or benchmarks the whole workspace and reports back site by site.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · Claude Code

You: The shared header changed on every client site. Use xSpeed Hub to clear all caches.

list_sites read-only
→ 12 sites in the default workspace

Claude Code: This will touch all 12 sites with a full purge. Go ahead?

You: Yes.

purge_cache(site: all, type: all) changes site
→ 11 of 12 purged; stage-acme timed out

Claude Code: Eleven sites are clear. stage-acme timed out, so I cannot confirm its cache was purged. I can retry just that one.

How Claude Code handles this

You run a portfolio of WordPress sites, maybe for clients, and you are already in the terminal because that is where you ship the change that touches all of them: a shared plugin update, a new default, a stale header. You tell Claude Code what you want done everywhere, and it calls one of the seven fan-out tools on xSpeed Hub with site set to "all": purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site or run_benchmark.

The Hub runs the sites one after another with a one-second pause, so twelve sites take about twelve seconds, and what returns is one result per site rather than a merged blob. If ten succeed and two time out, Claude Code can name the two and the error each gave instead of saying "done". Other tools do not fan out. get_health takes one site, so a diagnosis of all twelve is twelve calls that Claude Code makes itself.

Claude Code asks before it runs an MCP tool unless a permission rule already allows it, or you run in auto mode, where a classifier reviews actions instead of you, or in bypassPermissions mode, which asks nothing. In the default mode the all-sites purge appears as mcp__xspeedhub__purge_cache with site: "all" in its arguments, and you read it before you approve. For a purge, toggle, settings change or preloader call across every site, the Hub's own instructions also tell the agent to say "this will touch all 12 sites" once and wait for your answer. That is guidance to the model, not a lock, and it does not name optimize_site. Your approval and your connection's scope are the gates. The scope is read-only only if you connect with the connection token and turn Read-only everywhere on, or sign in as a Viewer member.

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.

Terminal

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.

Text

/mcp

1 / 3

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.

Prompt for Claude Code

Use xSpeed Hub to purge every site in my workspace, then list any site where the purge failed and why.

Prompt for Claude Code

With xSpeed Hub, run the benchmark on all sites and show me the three with the smallest gap between cached and uncached.

Prompt for Claude Code

Ask xSpeed Hub to start the preloader on every site except the staging ones, then check preloader status on each.

What happens, step by step

If you run many WordPress sites, repeating one action on each is the slow part. Through xSpeed Hub, seven tools accept every site in a workspace, or a list of handles, in a single call. The Hub runs the sites one after another and returns a result for each, so a site that fails is named instead of hidden. Everything else in the Hub works on one site per call.

See what you can reach

list_sites returns each site's handle, URL, status and scopes. When you have more than one workspace, list_workspaces returns each one's handle, id, your role, its site count, which one is the default, and whether this connection can reach it.

Choose the scope of the call

The agent passes site: "all" for every site in one workspace, or an array of handles for exactly those sites. For a workspace other than the default it also passes the workspace argument. Omit workspace and the call acts on the default workspace.

Confirm once

Before a purge, toggle, settings change or preloader call that touches every site, the Hub tells the agent to say "this will touch all N sites" and wait for you, then make one call. That instruction does not name optimize_site, so for it your client's prompt is the gate. It is guidance to the agent, not a lock. It is one tool call, so one approval in your client covers every site in it.

Run it as one call

The Hub runs the sites one after another with a one-second pause between live calls, so a fleet purge is not a burst of traffic at your servers. Revoked sites are skipped from "all". Each site's action lands in the activity log as its own row.

Read the result per site

The reply is a summary of targets, succeeded and failed, plus one row per site with ok and either its data or its error. Some sites failing is a partial success. Only a run where every site failed comes back as an error.

Follow up on the failures

The agent reports which sites failed and why, then retries just those handles with an array. Tools that read one site, such as get_cache_status and get_health, do not fan out, so a fleet-wide check means one call per site.

Reference

Fan-out tools	purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site, run_benchmark
Selector	site: "all", or an array of handles
What all covers	Every site this connection can see in one workspace, minus revoked ones
Pacing	One after another, with a 1 second pause between live calls
Result	summary (targets, succeeded, failed) and a row per site: ok, then data or error
Partial failure	Reported per site; the call counts as an error only when every site failed
Workspace argument	Optional. Omit it for the default workspace; name one by its handle or id from list_workspaces
Reach	Fixed when you approve the connection; list_workspaces shows reachable: false for the rest
Not fan-out	get_health, get_cache_status and every other tool take one site per call
Slow tools	optimize_site takes up to 2 minutes per site; a target_score run is capped at 12 rounds per call
Read-only	The connection token with Read-only everywhere on, or a Viewer sign-in, refuses every fan-out write; run_benchmark works. An OAuth sign-in gets the scopes the client asks for
Hub daily pass	Re-verifies sites, snapshots cache status and hit ratio, reads stored reports, alerts by Slack webhook or email

Rules worth keeping

Confirm once, then call once. The Hub has no confirmation step of its own, 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 that matter. The Hub's "this will touch all N sites" is an instruction to the agent for purge, toggle, settings and preloader calls, and it does not name optimize_site.
"all" is one workspace, never every workspace. To act in another workspace, name it. A write to a non-default workspace must name it, and an array of handles is looked up only in the workspace the call names.
Read every result per site. Treat some sites failing as a partial result, and never accept a blanket "done" from the agent.
Try a behaviour change on one site before you send it to the fleet. toggle_cache and update_settings on every site are one call, and each site checks values against its own settings, so a Pro setting can fail on a Free site.
optimize_site on many sites is slow, because each site can take up to two minutes inside one call. Use dry_run first, or name a short list of handles.
The Hub has no scheduler for agent prompts. Its own daily pass and alerts run without an agent, and an agent can only act when you send a prompt or your AI client runs one on a timer.

Good to know with Claude Code

A Claude Code allow rule names a tool, not its arguments. If you allowed mcp__xspeedhub__purge_cache so single-site purges stop prompting, the all-sites call is allowed too, and nothing in Claude Code tells them apart. Allow the reads by name, or with mcp__xspeedhub__get_* for every read that starts with get_, and keep the six fan-out tools that write (purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader and optimize_site) on a prompt. run_benchmark is a read, so it can sit on the allow list. Auto mode and bypassPermissions mode skip the prompt without any rule, so keep them for sessions that only read. Also remember that "all" stops at one workspace. If you manage client workspaces, say which one you mean, because a write to a workspace other than your default has to name it.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Use xSpeed Hub to list every site I can reach, and every workspace, and say which workspace you act in by default.

Prompt

With xSpeed Hub, purge the cache on every site in my workspace and tell me which ones failed.

Prompt

Use xSpeed Hub to run a benchmark on all my sites and rank them by cached response time.

Prompt

Use xSpeed Hub to start the preloader on blog, shop and docs only.

Prompt

With xSpeed Hub, turn page caching on for every site where it is off. Check each site first.

Prompt

Use xSpeed Hub to stop the preloader everywhere. The servers are busy.

Prompt

Ask xSpeed Hub to preview a safe optimize_site pass on every site with dry_run and summarize what it would change.

Prompt

Use xSpeed Hub to purge every site in the client-acme workspace, not my default one.

Frequently asked questions

Yes, for seven tools: purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. Claude Code sends one call with site set to all, and the Hub works through the workspace one site at a time and returns a result for each.

No. get_health takes a single site and does not accept all. Ask Claude Code to check several sites and it makes one call per site, which is fine inside the rate limit but takes longer than a fan-out call.

Every site the connection can see in one workspace. It never crosses workspaces, and revoked sites are skipped. If your connection is limited to some sites, "all" quietly means the sites you are allowed, with no error naming the rest. To act in another workspace, the agent names it with the workspace argument.

The other sites still run. The reply has a summary and a row for each site with ok and its data or its error, so a site that was unreachable is named. A run counts as an error only when every site failed. Ask the agent to retry just the failed handles.

No. get_health and get_cache_status take one site per call, so the agent loops. The tools that fan out are purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. The Hub dashboard has a fleet overview for health.

Yes, on its own. A daily pass re-verifies each site, retrying a failed probe once, snapshots cache status and hit ratio, and reads the PageSpeed and GTmetrix reports your sites already stored. It can alert you by Slack webhook or email when a site becomes unreachable, caching is switched off, the hit ratio falls below a floor you set, or a score regresses. Each alert fires once per incident, not every day.

The Hub has no confirmation step. Its instructions tell the agent to confirm once with you, saying how many sites a call will touch, but that is guidance and not a lock. Your AI client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are what stop a write. The instruction covers purge, toggle, settings and preloader calls, not optimize_site. The dashboard's own Purge all button does confirm before it runs.

No. It cannot add, remove or rename sites, change members, roles or billing, mint or rotate tokens, or widen the workspaces this connection reaches. Those stay in the Hub dashboard.

Manage every site at once, from Claude Code.

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

Open xSpeed Hub Claude Code setup

Manage every WordPress site at once with Claude Code

How Claude Code handles this

Set up Claude Code once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Manage every site at once, from Claude Code.