Manage Cloudflare caching with Kimi Code

Managing Cloudflare with Kimi Code means asking Moonshot AI's terminal agent, in the repository you deploy from, to check a site's Cloudflare link, purge the edge cache after a release or toggle development mode through xSpeed Hub.

cloudflare_verifypurge_cloudflareset_cloudflare_dev_modepurge_cacheget_settings

Last updated: October 2026

Example session · Kimi Code

You: Deployed the new header to shop. Use xSpeed Hub to switch Cloudflare development mode on while I tweak the CSS.

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

Kimi Code: The link on shop works. Development mode bypasses the edge for about three hours and slows shop for real visitors meanwhile. Switch it on?

You: Approve once.

set_cloudflare_dev_mode(site: shop, enabled: true) changes site
→ Development mode on, bypassing the edge for about 3 hours

Kimi Code: On. Reloads now show the origin. Say done and I will switch it off.

You: Done, switch it off.

set_cloudflare_dev_mode(site: shop, enabled: false) changes site
→ Development mode off

Kimi Code: Off on shop, about 40 minutes after it went on. The edge serves visitors again; purge it if the new CSS is not showing.

How Kimi Code handles this

You deploy a template change from the repository where kimi is running, reload the site logged out, and the old markup is still there. Ask Kimi Code to look at Cloudflare for that site. It calls mcp__xspeedhub__cloudflare_verify, which asks Cloudflare whether the token and Zone ID stored in xSpeed still resolve, and prints the answer beside the diff you just shipped. The check purges nothing.

Then it can clear things in the right order. When the server page cache holds the old page too, purge_cache comes first and purge_cloudflare second, so the edge does not refill from a stale copy. If you are about to iterate on CSS for a while, set_cloudflare_dev_mode with enabled true bypasses the edge for about three hours, so each reload shows the origin. Each of these takes one site per call, and none of the Cloudflare tools accepts site: "all".

Because the session stays open while you edit, you can switch development mode on, change a stylesheet, reload, change it again, and ask Kimi Code to switch it off at the end. No Hub tool reports whether dev mode is on, so the session history is your record of when it started. If dev mode fails while verify passed, the Cloudflare token probably lacks Zone Settings Edit.

Set up Kimi Code once

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

2Add xSpeed Hub to mcp.json

Put this in ~/.kimi-code/mcp.json to use the Hub in every project, or in .kimi-code/mcp.json inside one repository, where it overrides a user entry of the same name. You can also run /mcp-config and let Kimi Code add it. A server added while a session is open joins only the next session.

~/.kimi-code/mcp.json

{
  "mcpServers": {
    "xspeedhub": {
      "url": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}

3Sign in with /mcp-config login

Start a new session with kimi, run this and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste. Then run /mcp to check that xspeedhub is connected.

Text

/mcp-config login xspeedhub
/mcp

1 / 3

Full Kimi Code 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. In Kimi Code's default Always Ask mode, an MCP call that matches no permission rule asks for approval, and Approve for this session allows the same kind of call until the session ends. Permanent rules go in [[permission.rules]] in config.toml: allow mcp__xspeedhub__get_* and mcp__xspeedhub__list_* to let the reads run, and leave the write tools on the prompt. Ask When Needed mode, from /yolo, approves MCP calls automatically, and Never Ask, from /auto, approves everything. xSpeed Hub has no confirmation step of its own, so in either of those modes a purge or a settings change runs as soon as your connection allows writes. To remove writes altogether, list the read tools in the entry's enabledTools, or use a connection token with Read-only everywhere on.

What do I ask?

Three prompts written for Kimi Code. More for this job are below.

Prompt for Kimi Code

Use xSpeed Hub to verify the Cloudflare connection on shop and print exactly what came back.

Prompt for Kimi Code

I just deployed to blog. With xSpeed Hub, purge blog's page cache and then its Cloudflare edge.

Prompt for Kimi Code

Using xSpeed Hub, switch Cloudflare development mode on for shop while I work on this stylesheet, and off when I say done.

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 Kimi Code

In the default Always Ask mode, Kimi Code prompts for every MCP call that matches no permission rule, cloudflare_verify included. Add an allow rule in [[permission.rules]] for mcp__xspeedhub__cloudflare_verify and leave the two Cloudflare writes unmatched. Approve for this session on set_cloudflare_dev_mode means a later request in the same session can switch it again without asking. Ask When Needed, from /yolo, and Never Ask, from /auto, approve MCP calls automatically, and the Hub has no confirmation step of its own, so in those modes a live site can end up in development mode, slower for real visitors for about three hours. If a session should only inspect, put the read tools in the entry's enabledTools, or send a connection token with Read-only everywhere on through bearerTokenEnvVar. Never paste a Cloudflare token into the prompt; it belongs in the xSpeed Cache panel in wp-admin.

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

cloudflare_verify, which only reads and purges nothing. Add an allow rule for mcp__xspeedhub__cloudflare_verify in config.toml and leave purge_cloudflare and set_cloudflare_dev_mode on the prompt, because the Hub runs them as soon as the connection allows writes.

Verifying and purging do not need Zone Settings Edit on the Cloudflare token, but development mode writes a zone setting. Edit the token in Cloudflare so it has Zone Cache Purge and Zone Settings Edit, then ask Kimi Code to try again.

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 Kimi Code.

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

Open xSpeed Hub Kimi Code setup

Manage Cloudflare caching with Kimi Code

How Kimi Code handles this

Set up Kimi Code 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 Kimi Code.