How Muse handles this
The person this suits runs several WordPress sites and is often away from a desk: a shop owner with a blog and two landing sites, or a freelancer with a handful of clients. You send Muse a message such as "how are all my sites doing?" in WhatsApp. With xSpeed Hub added as a custom connector, Muse calls run_benchmark with site set to "all", or with a list of the handles you name, and the Hub measures each site's cached and uncached response time in turn, one second apart. The reply comes back in the same thread, one line per site.
A phone thread needs short answers, so ask for the outliers instead of the full table: the site that barely gains from its cache, the one that did not respond. The Hub returns ok and either data or an error for each site, so a fleet call where one site is unreachable is a partial success, and Muse can name that site. Seven tools accept every site at once, and six of them write: purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader and optimize_site. run_benchmark is the read among them, which makes it the right first fleet request.
The setup the Muse page recommends makes the first weeks safe by default. You give Muse the Hub's connection token, and with Read-only everywhere on, the Hub refuses every write tool on that token, so a fleet purge cannot run whatever Muse decides. Meta says Muse will not take many important actions without your approval by default, that you change when it asks in Settings, and that its Sentinel agent asks for permission when needed. xSpeed Hub has no confirmation step of its own, so once you switch Read-only everywhere off, those Muse settings and the Hub's instruction to confirm once before a fleet-wide purge, toggle, settings or preloader call are what stand before a change. That instruction is guidance, not a lock, and it does not name optimize_site.
Set up Muse once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Muse 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.
2Copy the connection token from xSpeed Hub
Sign in at app.xspeedcache.com as the workspace owner and open Connect AI. Copy the connection token. For a first try, turn on Read-only everywhere: the Hub then refuses every write tool on that token, so Muse can read but not purge or change settings.
xSpeed Hub > Connect AI > connection token (Read-only everywhere: on)
3Ask Muse to create a custom connector
Send this message to Muse in the app, on muse.ai or in WhatsApp, and follow the steps Muse gives you. When it asks for the credential, give it the token as a Bearer token. Meta does not review custom connectors, so only finish this for the request you started yourself.
Create a custom connector called xSpeed Hub for the MCP server at https://app.xspeedcache.com/xspeed/mcp It authenticates with a Bearer token in the Authorization header. Once it is connected, use xSpeed Hub to list my sites.
Full Muse 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. Meta says Muse will not take many important actions without your approval by default, that many connectors can be set up to only retrieve data, and that you change when Muse asks for approval in its Settings. Muse's separate Sentinel agent also decides what leaves its secure machine and asks you for permission when needed. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Muse calls it and your connection allows writes. The firm stop here is the token: with Read-only everywhere on, the Hub refuses every write tool, whatever Muse decides. Turn it off only when you want Muse to purge or change settings, and read each question Muse asks before you answer yes.
What do I ask?
Three prompts written for Muse. More for this job are below.
Use xSpeed Hub to benchmark all my sites and send me only the ones that look wrong.
With xSpeed Hub, tell me which of my sites did not respond to the last benchmark, one line each.
Ask xSpeed Hub for every site in my workspace and whether page caching is on for 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.
01
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.
02
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.
03
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.
04
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.
05
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.
06
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 Muse
Meta's pages describe no scheduled tasks for Muse, so a fleet check happens when you send the message, not on a timer. For a check that runs by itself, rely on the Hub's own daily pass, which re-verifies each site and can alert you by Slack webhook or email when a site becomes unreachable or caching is switched off. The connection token reaches every site in the workspace and only the workspace owner can see it, so turning Read-only everywhere off widens what Muse can do on all of them at once. Do it on purpose, for the change you want, and consider turning it back on afterwards. Rotating the token cuts off Muse and every other client that sends it. Muse is rolling out in the US first, and xSpeed Hub is a custom connector that Meta does not review, so create it only from a request you sent yourself. And "all" covers one workspace, so name a client workspace when you mean it.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to list every site I can reach, and every workspace, and say which workspace you act in by default.
With xSpeed Hub, purge the cache on every site in my workspace and tell me which ones failed.
Use xSpeed Hub to run a benchmark on all my sites and rank them by cached response time.
Use xSpeed Hub to start the preloader on blog, shop and docs only.
With xSpeed Hub, turn page caching on for every site where it is off. Check each site first.
Use xSpeed Hub to stop the preloader everywhere. The servers are busy.
Ask xSpeed Hub to preview a safe optimize_site pass on every site with dry_run and summarize what it would change.
Use xSpeed Hub to purge every site in the client-acme workspace, not my default one.
Frequently asked questions
Keep going
Manage every site at once with other agents
More with Muse
Documentation
- Managing your fleet with xSpeed Hub
- Teams, roles and workspaces in xSpeed Hub
- Scoped AI connections in xSpeed Hub
- Connecting to xSpeed Hub
- How to write prompts for xSpeed Hub
- Muse + xSpeed
- Every AI agent that works with xSpeed
From the blog