# Purge the WordPress cache with Manus

> Purging the WordPress cache with Manus means giving the agent a task whose last step clears the xSpeed cache on the right sites, through the xSpeed Hub custom MCP server you added in its Settings.

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

Manus takes a task from request to finished result, so a purge rarely arrives on its own. You hand it the release notes for a plugin update that went out to all your sites and ask it to check each changelog page, then clear the stale copies. It works through the steps, and when it reaches the cache it calls list_sites, then purge_cache with the type that fits, and folds the results into its final report. Name xSpeed Hub in the task, because Manus uses a custom server when the prompt mentions it.

The server was added under Settings, Integrations, Custom MCP Servers with the Hub's address and the connection token as the Bearer token, and Manus checked that it could read the tool list. For this job the token has to allow writes, so Read-only everywhere must be off on the Connect AI page. Each purge returns the plugin's report: the 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 task that purges several sites can use one call with every site, and the Hub returns a result per site.

Manus's custom MCP documentation describes no per-tool approval setting, and xSpeed Hub has no confirmation step of its own, so a purge runs once Manus calls it. The Hub tells Manus to confirm the target site and to ask once before a write that touches every site, and that is guidance to the model, not a lock. The practical gate is the task itself: write ask me before you purge into it, and Manus brings the plan back to you before it clears anything.

## Set up Manus 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. Copy the connection token from xSpeed Hub

Sign in at app.xspeedcache.com as the workspace owner, open Connect AI and copy the connection token. If Manus will only report, turn on Read-only everywhere so the Hub refuses every write tool on that token.

```
xSpeed Hub  >  Connect AI  >  connection token
```

### 3. Add xSpeed Hub as a custom MCP server

In Manus, open Settings, then Integrations, then Custom MCP Servers, and click Add Server. Name it xSpeed Hub, enter this as the server URL, and enter the connection token as the Bearer token in the authentication field.

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

### 4. Let Manus test it, then name it in a task

Manus checks that it can reach the server and read its list of tools. Then start a task that names xSpeed Hub, so Manus uses this server.

```
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
```

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

### 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. Manus's custom MCP documentation describes no per-tool approval setting for a custom server, and its scheduled tasks offer a skip confirmations option that lets Manus act without asking each time. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Manus 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. The firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Keep it on for scheduled work, and leave skip confirmations off for any task that may write.

## Prompts

- Use xSpeed Hub to purge the page cache on every site after the plugin update, and give me one line per site. Ask me once before you start.
- With xSpeed Hub, check the changelog page on docs, then purge only the page cache on that site.
- Ask xSpeed Hub for the cache status of shop, then propose a purge type for my theme change and wait for my yes.

## Example session

```
You: The plugin update is out on all sites. Use xSpeed Hub to clear the stale pages everywhere, and ask me before you purge.
  → list_sites [read-only]: 4 sites: shop, blog, docs, landing
Agent: A plugin update changes page output, so a page purge fits. That touches all 4 sites in one call. Purge the page cache on all 4?
You: Yes, go ahead.
  → purge_cache(site: all, type: page) [changes site]: 4 of 4 sites purged; 940 cached pages cleared in total
Agent: All four sites are clear, one result each. Want the preloader started on every site so the first visitors are not rebuilding pages?
```

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

Keep purges out of scheduled tasks. They run unattended, and Scheduled Tasks 2.0 has a skip confirmations option that lets Manus act without checking with you, so a recurring task with a write-capable token could purge every week with nobody reading the result first. The Read-only everywhere switch covers the whole connection token, so the token you use for releases is the same one a scheduled task would send: if it allows writes, any task that names xSpeed Hub can purge. Turn the switch on while you are not releasing if Manus mostly reports. Treat the token as a key to every site in the workspace, keep it out of chat messages, and rotate it on the Connect AI page if it leaks, which also cuts off any other client that sends 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 Manus purge my WordPress cache as part of a bigger task?

Yes. Add xSpeed Hub as a custom MCP server and name it in the task. Manus calls purge_cache when it reaches that step and puts the result per site into its report.

### Why does Manus get a refusal when it tries to purge?

The connection token is probably set to Read-only everywhere, and the Hub then refuses every write tool. That is the right setting for scheduled reports. For a purge, the workspace owner turns it off on the Connect AI page, which applies to every client sending that token.

### 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](https://xspeedcache.com/agent/grok/purge-cache/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/) · [Muse](https://xspeedcache.com/agent/muse/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 Manus

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