How Muse handles this
Muse is the agent you reach from your phone, so the purge happens away from the desk. You are out, someone on the team says the opening hours on docs are wrong even though the page was edited this morning, and you message Muse in WhatsApp. It calls list_sites to match the site, picks a page purge for a content edit, and runs purge_cache. The answer comes back in the same thread a moment later: which site, which type and how many pages were cleared.
The connector is the part that needs care for this job. Muse created it when you asked, and it keeps the Hub's connection token in its Secure Credentials Store. Many people start that token with Read-only everywhere on, which is the right default for a first try, and with it on the Hub refuses purge_cache outright, so Muse reports the refusal rather than a purge. To let Muse purge, the workspace owner turns that switch off on the Connect AI page, and the same token starts accepting writes. A purge of type all also reports the object cache and a connected Cloudflare edge, and Muse can start the preloader afterwards.
Meta says Muse will not take many important actions without your approval by default, that many connectors can be set to retrieve data only, and that you change when Muse asks in its Settings. Its separate Sentinel agent also decides what leaves Muse's secure machine and asks you for permission when needed. xSpeed Hub has no confirmation step of its own, so once Muse calls purge_cache on a token that allows writes, the purge runs. For a purge of every site, the Hub tells Muse to say it will touch all of them and wait for your yes, but that is guidance, not a lock.
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 purge the page cache on docs. The opening hours there were updated this morning.
With xSpeed Hub, read the cache status on shop and tell me whether a purge is needed. Do not purge yet.
Ask xSpeed Hub to purge the assets cache on blog, then start the preloader and tell me how many URLs it queued.
What happens, step by step
A purge throws away stored copies so the next visitor gets a fresh page. Through xSpeed Hub an agent can purge everything, only pages, only CSS and JavaScript assets, the object cache or the REST cache, on one site or across every site in a workspace. A full purge also clears the Cloudflare edge when the site has Cloudflare connected.
01
Find the site
The agent calls list_sites when you have more than one site, then matches the name you used to a site handle. If the name could mean two sites, the Hub tells it to ask you rather than guess.
02
Pick the purge type
purge_cache takes a type: all, page, assets, object or rest. all clears the page cache, the object cache and, when they are connected, the Cloudflare edge and CDN. After a theme or CSS change, assets is enough; after a content edit, page; after a deploy, all.
03
Purge
The call runs straight away on that site once your connection allows writes. For every site at once the agent passes site: "all", and the Hub runs the sites one after another with a one-second pause.
04
Clear only the edge if that is all you need
purge_cloudflare empties the Cloudflare edge cache on its own, without touching the copies on your server. A page or assets purge does not reach Cloudflare; a purge of type all does when Cloudflare is connected.
05
Warm it again
start_preloader rebuilds the cache in the background so the first visitors after the purge are not the ones paying for it.
Reference
| Tool | purge_cache (write) |
|---|---|
| Purge types | all, page, assets, object, rest |
| What all covers | Page cache, object cache, plus the Cloudflare edge and CDN when connected |
| Every site at once | site: "all" or a list of handles, one result per site |
| Fan-out pacing | Sites run one after another with a 1 second pause |
| Edge only | purge_cloudflare, a separate write tool |
| Re-warm | start_preloader after the purge |
| Read-only access | purge_cache is refused on a connection token with Read-only everywhere on, and for a Viewer sign-in |
| Confirmation | None on the Hub; your client's prompt is the gate |
Rules worth keeping
- Name the site. With several sites, an unclear name should make the agent ask, and the Hub tells it to.
- A purge of every site is one call with site: "all". The Hub tells the agent to confirm it with you once before it runs.
- Purge the narrowest type that fixes the problem, then warm the cache, so visitors do not all hit uncached pages at once.
- A fan-out result is reported per site. Treat some sites failing as a partial result, not a failure of the whole call.
Good to know with Muse
Turning Read-only everywhere off is all or nothing for that token. The Hub then accepts every write tool on it, toggle_cache and update_settings included, not only purges, and so does any other client that sends the same token. If you only want Muse to purge now and then, switch it off for the purge and back on afterwards, and remember that only the workspace owner sees the switch. Meta does not review custom connectors, so create this one only from a request you sent yourself, and check the server address when Muse shows it to you. Muse is rolling out in the US first, so the connector may not be available on your account yet.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to purge the page cache on blog.
I just changed the theme CSS on shop. Use xSpeed Hub to purge only the assets cache there.
With xSpeed Hub, purge every site in my workspace and tell me which ones failed.
Use xSpeed Hub to purge shop, then purge its Cloudflare edge cache too.
With xSpeed Hub, purge the docs site and start the preloader so it is warm again.
Using xSpeed Hub, what purge type should I use after updating a plugin that changes the checkout page?
Frequently asked questions
Keep going
Purge the cache with other agents
More with Muse
Documentation
- How to enable Page Cache
- How to warm your cache ahead of visitors
- Managing your fleet with xSpeed Hub
- How to write prompts for xSpeed Hub
- Muse + xSpeed
- Every AI agent that works with xSpeed
From the blog