How Grok Bot handles this
A Bot keeps context about the work you give it, so a purge can be a standing part of its job. You might have a Bot that looks after your marketing sites, and when you publish a landing page you message it: purge the page cache on landing and tell me what went. You attach the plugin with @xspeedhub, the Bot calls list_sites to match the name, then purge_cache with a type that fits, and it answers in the same chat once the call returns.
The plugin was added once from chat as a custom remote HTTPS MCP server, and because the Hub uses OAuth each person signs in with their own xSpeed Hub account. A plugin you add from your own chat is personal and account-wide, so every Bot on your account can purge with it. What comes back is the plugin's report: type, site, entries cleared, and for a purge of type all the object cache and a connected Cloudflare edge too. The Bot can follow with start_preloader and read get_preloader_status later, since its computer keeps running after you close the laptop.
When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, and from then on the same kind of call does not stop for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so an always-allowed purge_cache runs as soon as your connection allows writes. Add an Ask first rule for purge_cache and answer each one with Allow once. For a purge of every site the Hub also tells the Bot to confirm once, which is guidance, not a lock.
Set up Grok Bot once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Grok Bot 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.
2Ask your Bot to add xSpeed Hub
In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.
3Attach it and ask a first question
Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
Full Grok Bot 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. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.
What do I ask?
Three prompts written for Grok Bot. More for this job are below.
Use @xspeedhub (xSpeed Hub) to purge the page cache on landing and tell me how many pages were cleared.
With xSpeed Hub, purge only the assets cache on blog after my CSS change, then start the preloader.
Use xSpeed Hub to purge every site in my workspace and list any that failed. Ask me once before you start.
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 Grok Bot
Routines are the trap for this job. A routine runs on the Bot's cloud computer on a schedule with nobody watching, and xAI notes that a Test run performs real work, including calls to connected tools, so testing a routine that purges really purges. Keep routines to reads such as get_cache_status and do purges in a chat where you can answer the prompt. On a Team Bot only its owner changes the plugins in the Setup panel, and each teammate signs in to xSpeed Hub with their own account, so a teammate signed in as a Viewer member has purges refused while the owner's go through. The Hub's Read-only everywhere switch belongs to the connection token, which this OAuth plugin does not send. On a team plan, a Cursor connector policy can also block the plugin, which then shows as Disabled by team admin.
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 Grok Bot
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
- Grok Bot + xSpeed
- Every AI agent that works with xSpeed
From the blog