Manage every WordPress site at once with Claude Cowork

Managing every WordPress site at once with Claude Cowork means giving the desktop agent a fleet-wide task, such as benchmark and report, and letting it work through xSpeed Hub while you do something else.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · Claude Cowork

You: Using xSpeed Hub, give me a read of how all my sites perform with and without cache.

list_sites read-only
→ 7 sites in this workspace

run_benchmark(site: all) read-only
→ 6 benchmarked, each faster cached than uncached; trustsync unreachable

Claude Cowork: Six sites measured. Each of them answers faster cached than uncached. trustsync did not respond, so it has no figures.

How Claude Cowork handles this

Cowork suits the longer version of this job. You are an agency owner or a freelancer who wants a Monday read of the whole portfolio: which sites changed, which ones have caching off, how the cached and uncached response times compare. You describe the outcome, and Cowork plans the steps. It starts with list_sites, runs run_benchmark with site set to "all" for the response-time table, and then makes per-site reads for anything the fan-out tools do not cover.

Only seven tools accept "all": purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. Everything else is one site per call, so a task that also needs cache status or health reads becomes a longer chain, and Cowork works through it in the background. The Hub runs fan-out calls one site at a time with a one-second pause, and each answer comes back per site, so a single unreachable site shows up as one failed row.

Cowork uses the connectors on your Claude account, so add xSpeed Hub in Claude first. Cowork has three modes. Manual pauses and asks you to Allow or Deny each action, Auto keeps working and blocks what Claude judges unsafe, and Skip asks nothing. Each Hub tool also has its own setting of Always allow, Needs approval or Blocked. xSpeed Hub itself has no confirmation step and runs a write when your connection allows it, so decide up front whether this task should be read-only. The Hub's Read-only everywhere switch covers only the connection token, and Claude connectors sign in with OAuth, so for a read-only task sign in as a Viewer member or set the write tools to Blocked. When it finishes, ask Cowork to list the sites it could not reach, with the error for each, so you do not have to hunt for them in a long summary.

Set up Claude Cowork once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Claude Cowork 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 Claude account

Cowork does not keep its own connector list. In Claude, go to Customize > Connectors, click Add custom connector, name it xspeedhub, paste the URL, choose Sign in now and, if asked, Register automatically. The full steps, including the Team and Enterprise route, are on the Claude page: /agent/claude/.

Text

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

3Connect, then start a new Cowork session

Click Connect on the connector and approve access on the xSpeed Hub page. Cowork loads the connectors enabled for your account when a session starts, so open a new Cowork session after you connect. You can also switch the connector on from the + menu in the chat box.

Text

Customize  >  Connectors  >  xspeedhub  >  Connect

4Set tool permissions before the first task

Open the connector under Customize > Connectors and set each tool to Always allow, Needs approval or Blocked. A sensible start is Always allow for the read tools and Needs approval for purge_cache, toggle_cache, update_settings and the other writes. Then pick a Cowork mode; Manual is the one that shows you each request.

Text

Tool permissions: get_cache_status = Always allow
Tool permissions: purge_cache = Needs approval

1 / 4

Full Claude Cowork 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. Cowork has three modes. Manually approve (Manual) pauses and asks you to Allow or Deny each action. Automatically approve (Auto) keeps working and blocks what Claude judges to be unsafe. Skip all approvals (Skip) asks nothing and checks nothing. Each connector tool also has a permission, set under Customize > Connectors. In Manual mode, Always allow runs, Needs approval asks and Blocked is denied; in Skip mode only Blocked stops a call. xSpeed Hub has no confirmation step of its own, so under Skip, or for any tool set to Always allow, a write runs as soon as your connection allows writes. Auto relies on Claude's own judgement, which is not a lock.

What do I ask?

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

Prompt for Claude Cowork

Use xSpeed Hub to benchmark all my sites and write a short summary: the best and worst cached-versus-uncached gaps, and any site that failed.

Prompt for Claude Cowork

With xSpeed Hub, list my sites, check which have page caching off, and tell me before changing anything.

Prompt for Claude Cowork

Ask xSpeed Hub to turn page caching back on for the sites that have it off, and stop the preloader on any site where it is running.

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 Cowork

Add xSpeed Hub in Claude before you start a Cowork task, because Cowork reads the connectors on your Claude account and has no separate place to add one. Use Manual mode for a task that writes, and set the six fan-out tools that write to Needs approval. Skip asks nothing and checks nothing, so under Skip, or for a tool set to Always allow, a fleet-wide toggle is something you read about afterwards. Auto relies on Claude's own judgement, which is not a lock. Benchmarks are a safe starting task because run_benchmark is a read tool, even across all sites.

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, that is what it suits. Give it a task such as benchmark every site and summarize, and it works through xSpeed Hub in the background. In Manual mode a write waits for your Allow unless its tool is set to Always allow, because Hub itself runs a write once your connection allows it.

No. It uses the connectors on your Claude account, so you add xSpeed Hub in Claude once and Cowork can use it. If you want Cowork to only read, sign in to the connector as a Viewer member of the workspace, or set the write tools to Blocked, because the Hub's Read-only everywhere switch applies only to the connection token.

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 Cowork.

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 Cowork setup

Manage every WordPress site at once with Claude Cowork

How Claude Cowork handles this

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