# Purge the WordPress cache with Grok

> Purging the WordPress cache with Grok means asking xAI's chat assistant on grok.com to clear the xSpeed cache on a site you name, through the xSpeed Hub custom connector you added and signed in to once.

Page: https://xspeedcache.com/agent/grok/purge-cache/
Last updated: October 2026

Grok is a chat tab, so the purge usually starts as a complaint. A customer writes that the menu on shop still shows a category you removed an hour ago, and you open grok.com and type it in. Grok calls list_sites to match the name, chooses a purge type, and runs purge_cache through the connector. If you are not sure which cache holds the old copy, ask Grok to read get_cache_status first, which tells it whether page caching is on and how many pages are stored.

The connector was added once at grok.com/connectors as a Custom connector with the Hub's address, and the sign-in happened on an xSpeed Hub page, so Grok keeps the credentials and you paste nothing. What comes back is the plugin's report: the purge type, the site, how many entries were cleared, and for a purge of type all the object cache and a connected Cloudflare edge as well. A menu lives in every page's HTML, so a page purge covers it, while a stylesheet change would only need assets. Grok can then start the preloader so the next visitors find warm pages.

Approval is the part to understand before you rely on this. xAI's connector documentation describes no per-tool approval setting, and it says Grok can use a connector's tools whenever your question relates to that service. xSpeed Hub has no confirmation step of its own either, so a purge runs once Grok calls it and your connection allows writes. The Hub tells Grok to confirm the target site and to ask once before a write that touches every site, and that usually shows up as a question in the chat, but it is an instruction to the model, not a lock. Read what Grok says it is about to purge before you answer.

## Set up Grok 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 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
```

### 3. Ask 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 setup: https://xspeedcache.com/agent/grok/

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

## Prompts

- Use xSpeed Hub to purge the page cache on shop. The menu still shows a category I removed.
- With xSpeed Hub, read the cache status on blog first, then tell me which purge type my CSS change needs. Do not purge yet.
- Ask xSpeed Hub to purge every site in my workspace, but list them and wait for my yes before you run it.

## Example session

```
You: A customer says the menu on shop still shows the old category. Use xSpeed Hub to fix that.
  → list_sites [read-only]: 4 sites: shop, blog, docs, landing
  → get_cache_status(site: shop) [read-only]: page cache on, 296 cached pages
Agent: The menu is part of every page's HTML, so the stored pages on shop are what is stale. Purge the page cache on shop?
You: Yes.
  → purge_cache(site: shop, type: page) [changes site]: 296 cached pages cleared
Agent: Cleared. Every page on shop rebuilds with the new menu on its next visit. I can start the preloader to warm them now.
```

## How it works

1. **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.
2. **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.
3. **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.
4. **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.
5. **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

- 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

Because nothing in Grok holds a purge back, the connection is where you set the limit. A sign-in as a Viewer member of the workspace is read-only, and the Hub refuses purge_cache for it, so use that account for chats that should only look. The connection token's Read-only everywhere switch does not help here, because xAI describes no header field for a custom connector and Grok signs in with OAuth. A broad question about your sites can also lead Grok to reach for the connector on its own, so phrase a purge request with the site and the type, and say do not purge when you only want numbers. On Grok Business and Enterprise a team admin has to provision the connector before members can add it.

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

### Can Grok purge my WordPress cache?

Yes. Add xSpeed Hub as a custom connector on grok.com/connectors and sign in once. Then ask Grok to purge a named site; it calls purge_cache with a type that fits and reports what was cleared.

### Does Grok ask before it purges?

xAI describes no per-tool approval setting for connectors, and xSpeed Hub has no confirmation step of its own, so a purge runs once Grok calls it and your connection allows writes. The Hub tells Grok to confirm the site, which usually appears as a question, but that is not a lock. A sign-in as a Viewer member refuses every purge.

### What is the difference between the purge types?

all clears every cache xSpeed manages for the site, including a connected Cloudflare zone or CDN. page clears the stored HTML pages, assets clears minified and combined CSS and JavaScript, object clears the Redis or Memcached object cache, and rest clears cached REST API responses.

### Does purging xSpeed also clear Cloudflare?

A purge of type all does, when the site has Cloudflare connected in xSpeed: it clears the page cache, the object cache and the Cloudflare edge, and reports each one. A page, assets or rest purge stays on your server. purge_cloudflare clears only the edge.

### Can I purge all of my sites with one prompt?

Yes. The agent passes site: "all" to purge_cache and the Hub purges every site in the workspace one after another, returning a result per site. The Hub tells the agent to confirm a write across every site with you once before it runs it.

### Will a purge slow my site down?

The next request to each purged page builds it fresh, which is slower than a cached hit. Starting the preloader right after the purge rebuilds the cache in the background so visitors mostly land on warm pages.

## Purge the cache with other agents

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

## More with Grok

- [Find out why WordPress pages are not cached with Grok](https://xspeedcache.com/agent/grok/troubleshoot-cache/)
- [Scan a website for speed problems with Grok](https://xspeedcache.com/agent/grok/speed-scan/)
- [Run and track PageSpeed tests with Grok](https://xspeedcache.com/agent/grok/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Grok](https://xspeedcache.com/agent/grok/optimize-site/)
- [Tune WordPress cache settings with Grok](https://xspeedcache.com/agent/grok/cache-settings/)
- [Warm the WordPress cache with Grok](https://xspeedcache.com/agent/grok/preload-cache/)
- [Set up the Redis object cache with Grok](https://xspeedcache.com/agent/grok/object-cache/)
- [Manage Cloudflare caching with Grok](https://xspeedcache.com/agent/grok/cloudflare/)
- [Manage every WordPress site at once with Grok](https://xspeedcache.com/agent/grok/fleet/)

## Documentation

- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/
- How to warm your cache ahead of visitors: https://xspeedcache.com/docs/preloader/
- Managing your fleet with xSpeed Hub: https://xspeedcache.com/docs/managing-your-fleet-with-xspeed-hub/