# Manage Cloudflare caching with Claude

> Managing Cloudflare with Claude means asking the Claude chat app, in plain language, to verify a WordPress site's Cloudflare connection, purge its edge cache or switch development mode through the xSpeed Hub connector.

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

You are in a Claude conversation, probably after a customer or an editor told you a page looks out of date. You do not want to open another dashboard to find out whether Cloudflare is the cause. Describe the symptom and name the site. Claude matches the name to one of your connected sites, runs cloudflare_verify to see whether the Cloudflare credentials stored in xSpeed still resolve, and tells you what it found before anything else happens.

From there you choose. purge_cloudflare clears only the edge copy of the site, which is the right move when the server cache is already fresh. set_cloudflare_dev_mode bypasses the edge for about three hours so changes at the origin appear immediately, and it can be turned off again by asking. A purge_cache call of type all also clears the edge when Cloudflare is connected, so Claude may suggest that instead when you changed content as well as styles. None of the three Cloudflare tools accepts every site at once, so for several sites you will see Claude work through them one at a time.

Claude reports in the chat, so the result is easy to paste into a ticket: which site, which tool ran, and what Cloudflare answered. Add the connector under Customize, then Connectors, first, and switch it on from the plus menu in each conversation where you want it. On a Team or Enterprise plan an Owner adds it for the organization, and each member then connects with their own account.

## Set up Claude 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. Add xSpeed Hub as a custom connector

Go to Customize > Connectors and click Add custom connector. Name it xspeedhub and paste the URL. Under Authentication choose Sign in now, and if Claude asks how it identifies itself, choose Register automatically, which uses dynamic client registration. Click Add. On a Team or Enterprise plan an Owner does this under Organization settings > Connectors, with Add, then Custom, then Web.

```
https://app.xspeedcache.com/xspeed/mcp
```

### 3. Connect and turn it on in a chat

Click Connect on the xspeedhub connector and approve access on the xSpeed Hub page that opens. Then, in a conversation, click + in the message box, choose Connectors and switch xspeedhub on. Claude can use the connector only in conversations where that toggle is on.

```
+  >  Connectors  >  xspeedhub (on)
```

Full setup: https://xspeedcache.com/agent/claude/

### 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. Claude can ask for your approval before it uses a connector tool. Allow once runs that call, and Always allow skips the prompt for that tool from then on. Under Customize > Connectors you can set each tool, or a group of tools, to Always allow, Needs approval or Blocked. xSpeed Hub has no confirmation step of its own, so a write tool you set to Always allow runs as soon as your connection allows writes. Keep purge_cache, update_settings, toggle_cache and the other write tools on Needs approval, block the ones you never want. For read-only access, sign in as a Viewer member of the workspace, or use the connection token with Read-only everywhere on, which needs the Request headers beta. The switch does not apply to a normal OAuth sign-in.

## Prompts

- Using xSpeed Hub, is Cloudflare still connected on my shop site? Check it without changing anything.
- The pricing page on blog still shows last month's prices. Use xSpeed Hub to clear the Cloudflare cache for that site.
- With xSpeed Hub, turn Cloudflare development mode on for shop so I can test the new checkout, then off again when I say so.

## Example session

```
You: Editors say the pricing page on blog still shows the old prices. Using xSpeed Hub, could Cloudflare be serving it?
  → cloudflare_verify(site: blog) [read-only]: Credentials and zone resolve; Cloudflare connected
Agent: Cloudflare is connected on blog, so the edge can hold an old copy, and so can xSpeed's page cache on the server. Clearing only the edge would let it refill from that server copy. Purge blog's page cache first, then the Cloudflare edge?
You: Go ahead.
  → purge_cache(site: blog, type: page) [changes site]: page cache purged (64 entries)
  → purge_cloudflare(site: blog) [changes site]: Cloudflare edge cache purged
Agent: The server page cache and the Cloudflare edge are both cleared for blog, so the next request builds the pricing page fresh. Reload it in a private window to check.
```

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

Claude asks per tool: Allow once runs that call, and Always allow skips the prompt for that tool from then on. Under Customize, then Connectors, you can instead set each tool to Always allow, Needs approval or Blocked. Set cloudflare_verify to Always allow if you like, and keep set_cloudflare_dev_mode on Needs approval, because an Always allow means development mode can switch on in a later chat without a prompt, and it slows the site for real visitors for about three hours. The Hub's own instructions to the agent do not list set_cloudflare_dev_mode among the tools to confirm, so Claude's prompt is the check for it. Claude signs in with OAuth and gets the scopes it asks for, and the Hub's Read-only everywhere switch applies only to the connection token, which Claude can send only through the Request headers beta. For read-only access, sign in as a Viewer member of the workspace, or set both write tools to Blocked. Anthropic notes that Research can call connector tools without further approval, so set both writes to Blocked before you use Research with this connector.

## 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 I use Claude to check Cloudflare without letting it change anything?

Yes. cloudflare_verify is a read tool. Claude signs in with OAuth and gets the scopes it asks for, so the Hub's Read-only everywhere switch does not apply. A Viewer member's sign-in is always read-only and refuses purge_cloudflare and set_cloudflare_dev_mode, so Claude can report the state of the link but cannot purge or switch dev mode. You can also set those two tools to Blocked in Claude.

### Do I need a paid Claude plan to manage Cloudflare through xSpeed Hub?

No. The Free plan can add one custom connector, so xSpeed Hub fits if that slot is free. On Team and Enterprise plans an Owner adds the connector under Organization settings, then Connectors, and each member connects with their own account.

### 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 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/) · [Muse](https://xspeedcache.com/agent/muse/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 Claude

- [Purge the WordPress cache with Claude](https://xspeedcache.com/agent/claude/purge-cache/)
- [Find out why WordPress pages are not cached with Claude](https://xspeedcache.com/agent/claude/troubleshoot-cache/)
- [Scan a website for speed problems with Claude](https://xspeedcache.com/agent/claude/speed-scan/)
- [Run and track PageSpeed tests with Claude](https://xspeedcache.com/agent/claude/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Claude](https://xspeedcache.com/agent/claude/optimize-site/)
- [Tune WordPress cache settings with Claude](https://xspeedcache.com/agent/claude/cache-settings/)
- [Warm the WordPress cache with Claude](https://xspeedcache.com/agent/claude/preload-cache/)
- [Set up the Redis object cache with Claude](https://xspeedcache.com/agent/claude/object-cache/)
- [Manage every WordPress site at once with Claude](https://xspeedcache.com/agent/claude/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/