# Manage Cloudflare caching with Muse

> Managing Cloudflare with Muse means messaging Meta's personal agent, from its app, muse.ai or WhatsApp, to check a site's Cloudflare link through an xSpeed Hub custom connector, and purging the edge only once your token allows writes.

Page: https://xspeedcache.com/agent/muse/cloudflare/
Last updated: October 2026

An editor messages you that the live page still shows the old price, and you are nowhere near a laptop. In a Muse thread, from the app or in WhatsApp, you name the site and ask whether Cloudflare is the cause. Muse calls cloudflare_verify through the custom connector, which asks Cloudflare whether the token and Zone ID stored in xSpeed still resolve, and answers in a line or two. Nothing on the site changes during that check.

Whether Muse can go further depends on the connection token you gave it. With Read-only everywhere on, which is how the Muse setup suggests you start, the Hub refuses purge_cloudflare and set_cloudflare_dev_mode with a message saying the connection is read-only, and Muse can only report. Turn the switch off in the Hub and Muse can clear the edge cache for the site's zone, or bypass the edge for about three hours with development mode. When the server page cache is stale too, ask for purge_cache first so the edge does not refill from the old copy. None of these tools takes site: "all".

For a fix from a phone, a purge is usually the right tool and development mode the wrong one. Dev mode slows the site for every visitor for about three hours, no Hub tool reports whether it is on, and a reminder to switch it off is easy to lose in a phone thread.

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

- Using xSpeed Hub, is Cloudflare still connected on shop? Check only.
- Use xSpeed Hub to purge the page cache on blog and then its Cloudflare edge. The price page is stale.
- With xSpeed Hub, tell me which of my sites have a working Cloudflare connection, one at a time.

## Example session

```
You: Using xSpeed Hub, the price page on shop is stale for visitors. Is Cloudflare the reason?
  → cloudflare_verify(site: shop) [read-only]: Credentials and zone resolve; Cloudflare connected
Agent: Cloudflare is connected on shop, so its edge can hold the old price page, and so can xSpeed's page cache on the server. Purge the page cache on shop, then the Cloudflare edge?
You: Yes.
  → purge_cache(site: shop, type: page) [changes site]: This connection is read-only; write tools are not permitted.
Agent: The Hub refused the purge because this connector's token is read-only, so nothing changed and I did not try the edge. To let me purge, turn off Read-only everywhere on the token in the Hub, which also allows other writes, then ask again.
```

## How it works

1. **Verify the connection**: cloudflare_verify calls Cloudflare's API with the credentials stored on the site and checks that the token and zone still resolve. It purges nothing and works on a read-only connection. If Cloudflare is not connected on that site, the call comes back as an error and the agent should tell you rather than retry.
2. **Purge the edge**: purge_cloudflare empties the Cloudflare edge cache for the site's zone. It does not touch the copies on your server. When Cloudflare is in front of a site, a content change usually needs both, so the agent runs purge_cache first and purge_cloudflare after it, or one purge_cache of type all, which reaches the edge when Cloudflare is connected.
3. **Turn development mode on to see origin changes**: set_cloudflare_dev_mode with enabled true bypasses the edge for about three hours, so changes on the origin show immediately. It slows the site for real visitors the whole time. Your client's prompt is the gate here, because the Hub's instructions do not name this tool in their confirm list.
4. **Turn it off when you finish**: set_cloudflare_dev_mode with enabled false switches development mode off. Cloudflare also ends it on its own after about three hours. No Hub tool reads whether it is currently on, so note when you turned it on.
5. **Read a failure**: A rejected token, an empty zone ID or a refused call comes back as an error that names the action, the HTTP status and Cloudflare's message when it gave one. It is not reported as a success. The credentials themselves are set in the xSpeed Cache panel in wp-admin, not through the Hub.

## Reference

| | |
| --- | --- |
| Read tool | cloudflare_verify; purges nothing and works on a read-only connection |
| Write tools | purge_cloudflare and set_cloudflare_dev_mode (enabled true or false) |
| Needs | Cloudflare connected in xSpeed on that site: integration on, an API token (or the legacy key and email) and a Zone ID |
| Edge purge scope | Everything Cloudflare holds for the site's zone; the server copies stay |
| Development mode | Bypasses the edge for about 3 hours, then Cloudflare switches it off |
| Token permissions | Zone Cache Purge, and Zone Settings Edit for development mode |
| What verify proves | The token and zone resolve; a token without Zone Settings Edit still verifies |
| Through purge_cache | Type all also clears the edge when Cloudflare is connected; page, assets, object and rest do not |
| Every site at once | None of the three accept site: "all"; one site per call |
| Failure shape | An error with the action, the HTTP status and Cloudflare's message |
| Read-only connection | The connection token with Read-only everywhere on, or a Viewer member's sign-in; purge_cloudflare and set_cloudflare_dev_mode are refused and cloudflare_verify works. An OAuth sign-in gets the scopes the client asks for, so the switch does not make it read-only |
| Confirmation | None on the Hub; your client's prompt is the gate |

## Rules

- Run cloudflare_verify first, but do not read a pass as proof that every call will work. A token that lacks Zone Settings Edit verifies and purges fine, then fails the first time development mode is switched.
- Purge the server and the edge together after a content change. Purging only the site leaves visitors on the old page until the edge copy expires.
- Turn development mode off as soon as you are done. It slows the site for real visitors for up to about three hours, and no tool reports its state.
- Never paste a Cloudflare token or Global API Key into the chat. Connect Cloudflare in the xSpeed Cache panel in wp-admin, and use a scoped API token rather than the Global API Key.
- purge_cloudflare and set_cloudflare_dev_mode are write tools. The Hub runs them as soon as your connection allows writes, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer member's sign-in) are the gates that matter.

## Good to know with Muse

Meta says Muse will not take many important actions without your approval by default and that you change when it asks in its Settings, and its Sentinel agent checks what leaves Muse's secure machine. Those are Muse's controls, not the Hub's, and xSpeed Hub has no confirmation step of its own, so with writes allowed a purge runs as soon as Muse calls it. The Read-only everywhere switch covers every write tool at once: turning it off so Muse can purge Cloudflare also lets it purge server caches and change settings on every site the token reaches. If you only need an occasional purge, switch it off for the fix and back on after. Never paste a Cloudflare token into a Muse thread; Cloudflare credentials live in the xSpeed Cache panel in wp-admin. Meta does not review custom connectors, so create this one only from a request you sent yourself.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Use xSpeed Hub to check that the Cloudflare connection on shop still works.
- With xSpeed Hub, purge the Cloudflare edge cache on blog.
- I changed the checkout page on shop. Use xSpeed Hub to purge the site cache and the Cloudflare edge.
- Use xSpeed Hub to turn Cloudflare development mode on for shop. I am editing the theme.
- With xSpeed Hub, turn Cloudflare development mode off on shop.
- Ask xSpeed Hub to verify Cloudflare on shop and tell me what is wrong if it fails.
- Using xSpeed Hub, which of my sites have a working Cloudflare connection? Check them one at a time.

## Frequently asked questions

### Can Muse purge Cloudflare from WhatsApp?

Yes, if the connection token you gave Muse allows writes. With Read-only everywhere on, the Hub refuses purge_cloudflare and Muse can only verify the link. Turning the switch off allows the purge, and every other write tool too.

### Should I give Muse my Cloudflare API token?

No. Cloudflare credentials are set in the xSpeed Cache panel in wp-admin on each site, and the Hub uses them from there. Muse only needs the xSpeed Hub connection token for its custom connector.

### What does a site need before the Cloudflare tools work?

Cloudflare has to be connected in xSpeed on that site: the integration switched on, an API token (or the legacy Global API Key with your Cloudflare email) and the Zone ID of the domain. You set these in the xSpeed Cache panel in wp-admin. Without them, the tools return an error instead of acting.

### Does purging the xSpeed cache also clear Cloudflare?

A purge_cache of type all does, when the site has Cloudflare connected, and it reports each step. A page, assets, object or rest purge stays on your server. purge_cloudflare clears only the edge, so use it when the server copy is already fresh.

### How long does development mode last?

About three hours. Cloudflare switches it off on its own after that. While it is on, the edge is bypassed, so origin changes show at once and real visitors get a slower site. Turn it off yourself with set_cloudflare_dev_mode set to false when you are done.

### Why did cloudflare_verify pass but development mode failed?

Verifying and purging do not need Zone Settings Edit on the token, so a token without it looks fine. Development mode writes a zone setting, so it is refused. Edit the token in Cloudflare so it has both Zone Cache Purge and Zone Settings Edit, then try again.

### Can I purge Cloudflare on all my sites with one prompt?

Not with purge_cloudflare, which takes one site per call. A purge_cache of type all with site set to all clears the edge on each site that has Cloudflare connected, and the result is reported per site. The Hub tells the agent to confirm a write across every site with you once first.

## Manage Cloudflare with other agents

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

## More with Muse

- [Purge the WordPress cache with Muse](https://xspeedcache.com/agent/muse/purge-cache/)
- [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 every WordPress site at once with Muse](https://xspeedcache.com/agent/muse/fleet/)

## Documentation

- How to connect Cloudflare: https://xspeedcache.com/docs/cloudflare/
- How to serve assets from a CDN: https://xspeedcache.com/docs/cdn/
- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/