# Purge the WordPress cache with Muse

> Purging the WordPress cache with Muse means messaging Meta's personal agent, in its app, on muse.ai or in WhatsApp, to clear the xSpeed cache on a site through the xSpeed Hub custom connector it created for you.

Page: https://xspeedcache.com/agent/muse/purge-cache/
Last updated: October 2026

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

### 1. Put 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.

### 2. Copy 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)
```

### 3. Ask 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 setup: https://xspeedcache.com/agent/muse/

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

## Prompts

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

## Example session

```
You: The opening hours on docs are still the old ones. Use xSpeed Hub to clear the cached page.
  → list_sites [read-only]: 3 sites: shop, blog, docs
Agent: An edited page only needs the stored pages cleared. Purge the page cache on docs?
You: Yes.
  → purge_cache(site: docs, type: page) [changes site]: 112 cached pages cleared
Agent: Done, 112 pages cleared on docs. Open the page again and the new hours should show.
```

## How it works

1. **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.
2. **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.
3. **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.
4. **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.
5. **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

- 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

### Why does Muse say the purge was refused?

The connection token is probably set to Read-only everywhere, which makes the Hub refuse every write tool, purge_cache included. The workspace owner can turn that switch off on the Connect AI page in xSpeed Hub. Muse is reporting the Hub's refusal, not a problem with the connector.

### Can I purge my WordPress cache from WhatsApp with Muse?

Yes, once Muse has the xSpeed Hub custom connector and the token allows writes. Message Muse in WhatsApp, the Muse app or muse.ai with the site and what changed, and it calls purge_cache and replies with what was cleared.

### What is the difference between the purge types?

all clears every cache xSpeed manages for the site, including a connected Cloudflare zone or CDN. page clears the stored HTML pages, assets clears minified and combined CSS and JavaScript, object clears the Redis or Memcached object cache, and rest clears cached REST API responses.

### Does purging xSpeed also clear Cloudflare?

A purge of type all does, when the site has Cloudflare connected in xSpeed: it clears the page cache, the object cache and the Cloudflare edge, and reports each one. A page, assets or rest purge stays on your server. purge_cloudflare clears only the edge.

### Can I purge all of my sites with one prompt?

Yes. The agent passes site: "all" to purge_cache and the Hub purges every site in the workspace one after another, returning a result per site. The Hub tells the agent to confirm a write across every site with you once before it runs it.

### Will a purge slow my site down?

The next request to each purged page builds it fresh, which is slower than a cached hit. Starting the preloader right after the purge rebuilds the cache in the background so visitors mostly land on warm pages.

## Purge the cache with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/purge-cache/) · [Claude](https://xspeedcache.com/agent/claude/purge-cache/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/purge-cache/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/purge-cache/) · [Codex](https://xspeedcache.com/agent/codex/purge-cache/) · [Cursor](https://xspeedcache.com/agent/cursor/purge-cache/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/purge-cache/) · [Windsurf](https://xspeedcache.com/agent/windsurf/purge-cache/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/purge-cache/) · [Antigravity](https://xspeedcache.com/agent/antigravity/purge-cache/) · [Zed](https://xspeedcache.com/agent/zed/purge-cache/) · [Kiro](https://xspeedcache.com/agent/kiro/purge-cache/) · [OpenCode](https://xspeedcache.com/agent/opencode/purge-cache/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/purge-cache/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/purge-cache/) · [Grok Build](https://xspeedcache.com/agent/grok-build/purge-cache/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/purge-cache/) · [Grok](https://xspeedcache.com/agent/grok/purge-cache/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/) · [Manus](https://xspeedcache.com/agent/manus/purge-cache/) · [Kimi Code](https://xspeedcache.com/agent/kimi/purge-cache/) · [Paperclip](https://xspeedcache.com/agent/paperclip/purge-cache/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/purge-cache/)

## More with Muse

- [Find out why WordPress pages are not cached with Muse](https://xspeedcache.com/agent/muse/troubleshoot-cache/)
- [Scan a website for speed problems with Muse](https://xspeedcache.com/agent/muse/speed-scan/)
- [Run and track PageSpeed tests with Muse](https://xspeedcache.com/agent/muse/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Muse](https://xspeedcache.com/agent/muse/optimize-site/)
- [Tune WordPress cache settings with Muse](https://xspeedcache.com/agent/muse/cache-settings/)
- [Warm the WordPress cache with Muse](https://xspeedcache.com/agent/muse/preload-cache/)
- [Set up the Redis object cache with Muse](https://xspeedcache.com/agent/muse/object-cache/)
- [Manage Cloudflare caching with Muse](https://xspeedcache.com/agent/muse/cloudflare/)
- [Manage every WordPress site at once with Muse](https://xspeedcache.com/agent/muse/fleet/)

## Documentation

- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/
- How to warm your cache ahead of visitors: https://xspeedcache.com/docs/preloader/
- Managing your fleet with xSpeed Hub: https://xspeedcache.com/docs/managing-your-fleet-with-xspeed-hub/