Manage every WordPress site at once with Claude

Managing every WordPress site at once with Claude means typing one request in the chat app and letting xSpeed Hub run that action across the whole workspace, one site after another, with a result for each.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · Claude

You: Use xSpeed Hub to start warming the cache on all my sites.

list_sites read-only
→ 9 sites in this workspace

Claude: This will touch all 9 sites by starting the preloader on each. Continue?

You: Yes, go.

start_preloader(site: all) changes site
→ 8 started; embedpress refused, preloader module is off

Claude: Warming started on 8 sites. embedpress has the preloader module switched off, so nothing ran there.

How Claude handles this

The reader here is often an agency lead or a site owner with a dozen WordPress installs who would rather ask than log in to each one. You open Claude, with the xSpeed Hub connector added, and write something like "warm the cache on all my sites". Claude calls start_preloader with site set to "all", and the Hub starts the preloader on every site in the workspace you connected, one after another with a one-second pause.

The answer comes back as one result per site, and Claude turns that into a short table in the chat: which sites started, which refused, and the reason for each refusal. A site whose preloader module is switched off refuses on its own, and the other sites still run. That is a partial success, and Claude should report it as one. Only seven tools take "all". Reading a single site's health, settings or score history still needs a site name.

Claude can ask for your approval before it uses a connector tool, with the choices Allow once and Always allow, and in the connector's settings you can set each tool to Always allow, Needs approval or Blocked. For a purge, toggle, settings or preloader call that touches every site, the Hub also tells Claude to confirm once, with the number of sites, before it sends the request. It does not name optimize_site, so for that tool the approval prompt is the gate. Treat the prompt as your check. Claude signs in with OAuth and gets the scopes it asks for, read and write by default, and the Hub's Read-only everywhere switch applies only to the connection token, which the connector cannot send unless you use the Request headers beta. For a reports-only start, sign in as a Viewer member of the workspace, or keep every write tool on Needs approval or Blocked.

Set up Claude once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Claude 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 as a custom connector

Go to Customize > Connectors and click Add custom connector. Name it xspeedhub and paste the URL. Under Authentication choose Sign in now, and if Claude asks how it identifies itself, choose Register automatically, which uses dynamic client registration. Click Add. On a Team or Enterprise plan an Owner does this under Organization settings > Connectors, with Add, then Custom, then Web.

Text

https://app.xspeedcache.com/xspeed/mcp

3Connect and turn it on in a chat

Click Connect on the xspeedhub connector and approve access on the xSpeed Hub page that opens. Then, in a conversation, click + in the message box, choose Connectors and switch xspeedhub on. Claude can use the connector only in conversations where that toggle is on.

Text

+  >  Connectors  >  xspeedhub (on)

1 / 3

Full Claude 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 can ask for your approval before it uses a connector tool. Allow once runs that call, and Always allow skips the prompt for that tool from then on. Under Customize > Connectors you can set each tool, or a group of tools, to Always allow, Needs approval or Blocked. xSpeed Hub has no confirmation step of its own, so a write tool you set to Always allow runs as soon as your connection allows writes. Keep purge_cache, update_settings, toggle_cache and the other write tools on Needs approval, block the ones you never want. For read-only access, sign in as a Viewer member of the workspace, or use the connection token with Read-only everywhere on, which needs the Request headers beta. The switch does not apply to a normal OAuth sign-in.

What do I ask?

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

Prompt for Claude

Use xSpeed Hub to warm the cache on all my sites, then tell me which ones refused.

Prompt for Claude

Using xSpeed Hub, which of my sites has caching turned off? Check each one, then turn it back on for those only.

Prompt for Claude

With xSpeed Hub, benchmark every site and put the cached and uncached times in one table.

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

Choose Allow once, not Always allow, for the write tools, or leave them on Needs approval. An Always allow choice on purge_cache or start_preloader covers the all-sites form of that tool as well, so the next fleet-wide call runs without a prompt. Your plan also decides who can add the connector: the Free plan allows one custom connector, and on Team or Enterprise an owner adds it for the organization and each member then connects with their own account. Anthropic also notes that Research can call connector tools without further approval, so set the Hub's write tools to Blocked, or sign in as a Viewer member, before you use Research with this connector.

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, once the xSpeed Hub connector is added to your account. Ask for a purge, a preload or a benchmark on all sites and Claude sends one fan-out call. Sites that do not belong to the workspace you connected are not reached.

It should. The Hub returns a result for each site with an ok flag and either data or an error, and the Hub tells Claude to report failures by site instead of calling the run done. Ask it to list the failed sites and their errors if the summary is vague.

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.

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 setup

Manage every WordPress site at once with Claude

How Claude handles this

Set up Claude 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.