How Grok handles this
Someone tells you the homepage still shows last week's banner, and you suspect the copy Cloudflare keeps at the edge. In a Grok chat you describe the symptom and name the site. Grok matches the name with list_sites, calls cloudflare_verify to ask Cloudflare whether the token and Zone ID stored in xSpeed still resolve, and tells you the result. That check is a read and purges nothing, so it is a safe first step before anything changes.
From there you choose. purge_cloudflare clears the edge cache for the site's zone and leaves the copies on your server alone. If the server page cache is stale too, the edge refills from it, so the usual order is purge_cache first and purge_cloudflare after, or one purge_cache of type all, which reaches the edge when Cloudflare is connected. set_cloudflare_dev_mode with enabled true bypasses the edge for about three hours so origin changes show at once. None of the three Cloudflare tools accepts site: "all", so several sites mean several calls.
All three need Cloudflare connected in xSpeed on that site: the integration on, an API token and the Zone ID, set in the xSpeed Cache panel in wp-admin. If verify fails, Grok gets an error with the HTTP status and Cloudflare's message, and the fix is in wp-admin, not in the chat. Never paste a Cloudflare token into the conversation.
Set up Grok once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Grok 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.
2Add xSpeed Hub as a custom connector
Go to grok.com/connectors, click New Connector and select Custom. Enter this as the MCP server URL and complete the authentication: approve access on the xSpeed Hub page that opens. Grok then reads the Hub's tools and makes them available in your conversations.
https://app.xspeedcache.com/xspeed/mcp
3Ask a first question
Start a chat and ask something that names xSpeed Hub, so Grok reaches for the connector. A list of your sites with their cache status means the connection works.
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
Full Grok 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. xAI's connector documentation describes no per-tool approval setting. It says Grok can use a connector's tools whenever your questions relate to that service. xSpeed Hub has no confirmation step of its own, so a purge or a settings change runs as soon as Grok calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, but that is an instruction, not a lock. If you want Grok to read and never change anything, sign in as a Viewer member of the workspace, which only ever gets read access. Otherwise read what Grok says it is about to do before you answer yes.
What do I ask?
Three prompts written for Grok. More for this job are below.
Using xSpeed Hub, is the Cloudflare connection on shop still working? Verify only.
The banner on blog is stale. Use xSpeed Hub to purge blog's page cache and then its Cloudflare edge.
With xSpeed Hub, turn Cloudflare development mode on for shop while I edit, and tell me how to turn it off.
What happens, step by step
When Cloudflare sits in front of a WordPress site, it keeps its own copy of your files at the edge. Through xSpeed Hub an agent can check that the site's Cloudflare credentials still work, purge the edge cache, and turn development mode on or off. All three need Cloudflare connected in xSpeed on that site, and each works on one site at a time.
01
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.
02
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.
03
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.
04
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.
05
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 worth keeping
- 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 Grok
xAI describes no per-tool approval setting for connectors and says Grok can use a connector's tools whenever your question relates to that service. For Cloudflare that matters most with development mode: a request like "make sure visitors see my changes" could end in set_cloudflare_dev_mode, which slows the site for real visitors for about three hours, and the Hub runs it as soon as your connection allows writes, because it has no confirmation step of its own. The Hub's instructions to the agent do not name that tool in their confirm list either. Say exactly what you want, verify only or purge the edge, and read Grok's plan before you answer yes. No Hub tool reports whether dev mode is on, so note when it was switched. For a Grok that can verify but never purge, sign in as a Viewer member of the workspace; the connection token does not apply, because the connector uses OAuth.
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
Keep going
Manage Cloudflare with other agents
More with Grok
Documentation
- How to connect Cloudflare
- How to serve assets from a CDN
- How to enable Page Cache
- How to write prompts for xSpeed Hub
- Grok + xSpeed
- Every AI agent that works with xSpeed
From the blog