How ChatGPT handles this
ChatGPT is where many people already keep a running conversation about their site, so the purge happens mid-thread. You were just talking through why a product page loads an old image, and you say: clear it. ChatGPT calls list_sites to match the site, then purge_cache. If the stale copy might sit at the edge, it can also use purge_cloudflare, which clears only the Cloudflare edge and works only on a site with Cloudflare connected in xSpeed.
The tool call and its result show up in the conversation, so you can read what was sent and what came back: the purge type, the site, and how many entries were cleared. A purge of type all reports the page cache, the object cache and the edge separately, which makes it easy to tell which store held the old copy. ChatGPT is also good at the follow-up: ask it to start the preloader, then report the cache status.
ChatGPT asks you to confirm write actions by default, and it treats a tool without a read-only annotation as a write action. The Hub's tools carry no such annotation, so expect a confirmation on list_sites and get_cache_status as well as on purge_cache. You can expand a call to read the JSON it will send, and you can tell ChatGPT to remember an approval for a tool for the rest of the conversation. After that, purge_cache runs without a prompt, because xSpeed Hub runs a write as soon as your connection allows it.
Set up ChatGPT once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the ChatGPT 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.
2Turn on developer mode
In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode. On a Business workspace only admins and owners can use it. On Enterprise and Edu an admin grants access first, and you then turn it on under Settings, Apps, Advanced settings.
Settings > Security and login > Developer mode
3Create the app from the Hub URL
Open ChatGPT Plugins, select the plus button and create a developer-mode app. Name it xspeedhub, paste the MCP server URL and choose OAuth. Click Scan Tools, approve access on the xSpeed Hub page that opens, wait for the scan to list the tools, then click Create. Workspace admins can also start from Workspace settings, Apps, Create.
https://app.xspeedcache.com/xspeed/mcp
4Select the app in a chat
The app appears under Drafts in your app settings with a Dev label. In a new chat, open the plus menu in the composer, choose Developer mode and select xspeedhub. In a workspace, only an admin or owner can publish the app for other members.
+ > Developer mode > xspeedhub
Full ChatGPT 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. ChatGPT asks you to confirm write actions by default. You can expand a tool call to read the JSON it will send, and you can choose to remember an approve or deny choice for a tool for the rest of that conversation. ChatGPT respects a tool's read-only annotation and treats a tool without one as a write action; xSpeed Hub's tool definitions do not declare that annotation today, so expect confirmations on reads as well. OpenAI says confirmation also depends on app permissions and context, and some especially risky actions can be blocked. xSpeed Hub has no confirmation step of its own, so once you tell ChatGPT to remember Approve for a tool, that tool runs without a prompt for the rest of the conversation, as soon as your connection allows writes.
What do I ask?
Three prompts written for ChatGPT. More for this job are below.
The product page on shop shows an old image. Use xSpeed Hub to purge everything there, including Cloudflare if it is connected.
Which purge type should I use after changing a checkout plugin? Explain, then run it on shop with xSpeed Hub.
With xSpeed Hub, purge every site in my workspace and tell me which ones failed.
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 ChatGPT
OpenAI's pages differ on plans. The developer-mode guide lists Pro, Plus, Business, Enterprise and Edu on the web, while the help center calls full MCP with write actions a beta for Business, Enterprise and Edu and says Pro connects with read access. If ChatGPT can list your sites and read cache status but cannot purge, the plan is the likely reason, and it is separate from your role in the xSpeed workspace. A Viewer member's sign-in is read-only and refuses purges with its own message, which tells you which side said no. ChatGPT 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 ChatGPT cannot send. For read-only access, sign in as a Viewer member of the workspace, or keep ChatGPT's own confirmations on. Ask ChatGPT for the exact error text, then check the plan and your role, in that order. Custom MCP apps work on the web only, and agent mode does not use them, so run the purge from a normal chat.
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 ChatGPT
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
- ChatGPT + xSpeed
- Every AI agent that works with xSpeed
From the blog