Manage Cloudflare caching with Manus

Managing Cloudflare with Manus means handing the general agent a multi-site Cloudflare chore: it verifies every link through xSpeed Hub, writes up which sites fail and why, and purges the edge only on the sites you name.

cloudflare_verifypurge_cloudflareset_cloudflare_dev_modepurge_cacheget_settings

Last updated: October 2026

Example session · Manus

You: Use xSpeed Hub to check Cloudflare on all my sites before launch, then purge the edge on shop only.

list_sites read-only
→ 4 sites: shop, blog, docs, landing

cloudflare_verify(site: shop) read-only
→ Credentials and zone resolve; Cloudflare connected

cloudflare_verify(site: blog) read-only
→ error: Cloudflare is not connected on this site

cloudflare_verify(site: docs) read-only
→ Credentials and zone resolve; Cloudflare connected

cloudflare_verify(site: landing) read-only
→ error: verify failed, HTTP 403, Cloudflare says the token is invalid

Manus: shop and docs resolve. blog has no Cloudflare connection in xSpeed, and landing's token was rejected, which needs fixing in wp-admin. For shop: purge the server page cache, then the Cloudflare edge?

You: Yes, shop only.

purge_cache(site: shop, type: page) changes site
→ page cache purged (52 entries)

purge_cloudflare(site: shop) changes site
→ Cloudflare edge cache purged

Manus: Both caches are cleared on shop. The report lists landing's rejected token as the one item to fix before launch.

How Manus handles this

Manus suits the Cloudflare job with many small steps. You have a dozen sites, some behind Cloudflare and some not, and you want to know which links still work before a launch. Give Manus the task and name xSpeed Hub, so it uses the custom MCP server you added. It lists your sites, calls cloudflare_verify on each one, one call per site, and sorts the answers: links that resolve, sites with Cloudflare not connected in xSpeed, and sites where Cloudflare rejected the token, with the HTTP status and Cloudflare's message.

Then it writes the result as a document you can forward, which is what Manus adds over a chat. A failed site needs a person: the Cloudflare credentials are set in the xSpeed Cache panel in wp-admin on that site, not through the Hub, and a Cloudflare token should never go into the task text. Ask Manus to note one more limit in the write-up: a token without Zone Settings Edit still verifies and purges, then fails when development mode is switched, so a pass is not proof that dev mode will work.

If the launch also needs fresh caches, add that to the task with the site names: purge_cache on the server first, then purge_cloudflare for the edge, site by site, because none of the Cloudflare tools accepts site: "all". A purge_cache of type all also reaches the edge when Cloudflare is connected, and that tool does accept every site at once.

Set up Manus once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Manus 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.

2Copy 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.

Text

xSpeed Hub  >  Connect AI  >  connection token

3Add 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.

Text

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

4Let 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.

Text

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

1 / 4

Full Manus 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. 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.

What do I ask?

Three prompts written for Manus. More for this job are below.

Prompt for Manus

Use xSpeed Hub to verify Cloudflare on every site and write a short report of which links fail and why. Change nothing.

Prompt for Manus

With xSpeed Hub, purge the page cache and then the Cloudflare edge on shop and landing only, and log each result.

Prompt for Manus

Every Monday, use xSpeed Hub to run cloudflare_verify on each site and send me only the failures.

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.

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.

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.

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.

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.

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 Manus

Manus describes no per-tool approval setting for a custom MCP server, and xSpeed Hub has no confirmation step of its own, so once Manus decides a purge or development mode is part of the task, it runs as soon as your connection allows writes. Write the boundaries into the task: verify everything, purge only the sites I list, never switch development mode. Dev mode slows a live site for about three hours, and no Hub tool reports whether it is on. For a scheduled Cloudflare check, leave skip confirmations off and send the task through a connection token with Read-only everywhere on; the Hub then refuses purge_cloudflare and set_cloudflare_dev_mode, and cloudflare_verify still works. The token reaches every site in the workspace, so keep it out of chats and rotate it on the Connect AI page if it leaks.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Use xSpeed Hub to check that the Cloudflare connection on shop still works.

Prompt

With xSpeed Hub, purge the Cloudflare edge cache on blog.

Prompt

I changed the checkout page on shop. Use xSpeed Hub to purge the site cache and the Cloudflare edge.

Prompt

Use xSpeed Hub to turn Cloudflare development mode on for shop. I am editing the theme.

Prompt

With xSpeed Hub, turn Cloudflare development mode off on shop.

Prompt

Ask xSpeed Hub to verify Cloudflare on shop and tell me what is wrong if it fails.

Prompt

Using xSpeed Hub, which of my sites have a working Cloudflare connection? Check them one at a time.

Frequently asked questions

Yes. It calls cloudflare_verify once per site, since none of the Cloudflare tools accept every site at once, and can write the results up as a report. The check only reads, so it suits a scheduled task too.

Say so in the task, because Manus describes no per-tool approval for a custom server and the Hub has no confirmation step. For a firm stop, use a connection token with Read-only everywhere on, which makes the Hub refuse set_cloudflare_dev_mode and the purges.

Cloudflare has to be connected in xSpeed on that site: the integration switched on, an API token (or the legacy Global API Key with your Cloudflare email) and the Zone ID of the domain. You set these in the xSpeed Cache panel in wp-admin. Without them, the tools return an error instead of acting.

A purge_cache of type all does, when the site has Cloudflare connected, and it reports each step. A page, assets, object or rest purge stays on your server. purge_cloudflare clears only the edge, so use it when the server copy is already fresh.

About three hours. Cloudflare switches it off on its own after that. While it is on, the edge is bypassed, so origin changes show at once and real visitors get a slower site. Turn it off yourself with set_cloudflare_dev_mode set to false when you are done.

Verifying and purging do not need Zone Settings Edit on the token, so a token without it looks fine. Development mode writes a zone setting, so it is refused. Edit the token in Cloudflare so it has both Zone Cache Purge and Zone Settings Edit, then try again.

Not with purge_cloudflare, which takes one site per call. A purge_cache of type all with site set to all clears the edge on each site that has Cloudflare connected, and the result is reported per site. The Hub tells the agent to confirm a write across every site with you once first.

Manage Cloudflare, from Manus.

xSpeed Hub is free and has no site cap. Connect your sites once and ask from the agent you already use.

Open xSpeed Hub Manus setup

Manage Cloudflare caching with Manus

How Manus handles this

Set up Manus once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Manage Cloudflare, from Manus.