Manage every WordPress site at once with NanoClaw

Managing every WordPress site at once with NanoClaw means messaging your self-hosted agent with its trigger word in a chat app and letting it call xSpeed Hub across the whole workspace, one site after another.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · NanoClaw

You: @Andy use xSpeed Hub to stop the preloader everywhere, the servers are under load.

list_sites read-only
→ 6 sites in the workspace

NanoClaw: That stops the preloader on all 6 sites. Stop all 6?

You: Yes, all six.

stop_preloader(site: all) changes site
→ 5 stopped; 1 was already idle

NanoClaw: Five preloaders stopped and one was already idle. Pages that were already warmed stay cached, so visitors still get fast pages.

How NanoClaw handles this

NanoClaw lives in the chat app you already use, which suits a developer or small agency that runs its own tools. Your agent group has xSpeed Hub as one MCP server, sent the connection token as a Bearer header, and you talk to it with the trigger word, @Andy by default. During a traffic spike you write "@Andy use xSpeed Hub to stop the preloader everywhere". The agent calls stop_preloader with site set to "all", the Hub works through the workspace one site at a time with a one-second pause, and the reply in the chat names what happened on each site.

A chat reply has to be short, so ask for the exceptions: the sites that refused, the ones that did not answer. The Hub returns ok and either data or an error per site, so one unreachable site is one line in the reply, not a failed run. The seven fan-out tools are purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark, and only run_benchmark is a read. Questions about one site's settings or health take one call per site, which the agent makes on its own.

Whether NanoClaw asks you before an MCP call runs depends on your fork and its admins; its documentation gates adding a server behind approval but describes no per-tool prompt for calls. xSpeed Hub has no confirmation step of its own. The Hub's instruction to confirm once before a purge, toggle, settings or preloader call on every site shows up as a question in the chat, as in the session below, and you answer it there. It is an instruction to the model, not a lock, and it does not name optimize_site. The firm stop is the token: with Read-only everywhere on, the Hub refuses every fan-out write.

Set up NanoClaw once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the NanoClaw 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 agent group

Copy the connection token from Connect AI in the Hub (only the workspace owner sees it). Then run this on the machine that hosts NanoClaw, with your agent group's ID from ncl groups list. The header goes in as a JSON object, because NanoClaw refuses credentials inside the URL. NanoClaw may ask an admin to approve the change.

Terminal

ncl groups config add-mcp-server --id <group-id> --name xspeedhub \
  --url https://app.xspeedcache.com/xspeed/mcp \
  --headers '{"Authorization":"Bearer <your connection token>"}'

3Restart the group and ask

The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask something that names xSpeed Hub.

Terminal

ncl groups restart --id <group-id>

1 / 3

Full NanoClaw 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. Whether NanoClaw asks you before an MCP tool runs depends on how your fork and its admins are set up; its documentation gates adding a server behind approval but describes no per-tool prompt for calls. xSpeed Hub has no confirmation step of its own, so a write runs as soon as the agent calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, which in NanoClaw shows up as a question in the chat. The firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Keep it on for scheduled tasks.

What do I ask?

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

Prompt for NanoClaw

@Andy use xSpeed Hub to benchmark every site and reply with only the ones that look wrong.

Prompt for NanoClaw

@Andy with xSpeed Hub, stop the preloader on every site and tell me which were already idle.

Prompt for NanoClaw

@Andy ask xSpeed Hub to start the preloader on blog, shop and docs only.

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 NanoClaw

Scheduled tasks are the risky place for fleet writes. ncl tasks create runs a prompt on a cron schedule in the agent group's own session, with no chat attached and nobody to answer a question, so keep scheduled prompts to run_benchmark and other reads, name the chat that should receive the report, and send them through a token with Read-only everywhere on. The switch belongs to the token, so every agent group that sends the same token gets the same scope: turn it off for a fleet change you are watching, and back on before the next scheduled run. The token sits in the group's container configuration on your host, so keep the machine and its backups private, or hold it in NanoClaw's credential gateway. Rotating the token cuts off every client that sends it, and "all" covers one workspace, so name a client workspace in the message when you mean 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 the seven Hub tools that accept every site. Send one message with the trigger word and the agent makes one call, and the Hub returns a result per site that the agent can sum up in the chat.

No. A scheduled task has no chat attached and nobody to answer, so keep it to reads such as run_benchmark and send it through a token with Read-only everywhere on. Make fleet changes from a chat message you are watching.

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

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

Open xSpeed Hub NanoClaw setup

Manage every WordPress site at once with NanoClaw

How NanoClaw handles this

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