Manage Cloudflare caching with Kiro

Managing Cloudflare with Kiro means asking it, in the editor where you build your project, to verify a WordPress site's Cloudflare link, purge the edge cache or toggle development mode through xSpeed Hub.

cloudflare_verifypurge_cloudflareset_cloudflare_dev_modepurge_cacheget_settings

Last updated: October 2026

Example session · Kiro

You: The updated pricing table on shop is not showing for logged-out visitors. Using xSpeed Hub, is Cloudflare involved?

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

Kiro: Cloudflare is connected on shop, so it can serve a stored copy, and so can xSpeed's page cache on the server. Purge shop's page cache first, then run purge_cloudflare to clear the edge?

You: Yes, both.

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

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

Kiro: The server page cache and the Cloudflare copy for shop are both cleared. Reload logged out to check the table.

How Kiro handles this

You are working in Kiro, and the site you pushed to still shows an earlier version to visitors. You ask the agent to look at Cloudflare for that site by name. It calls list_sites to match the handle, then cloudflare_verify, which asks Cloudflare whether the stored token and zone still resolve. Nothing on the site changes during that check.

If the link is fine, the agent can call purge_cloudflare to clear only the edge copy, or set_cloudflare_dev_mode to bypass the edge for about three hours so changes at your origin show immediately. Both writes need Cloudflare connected in xSpeed on that site, and neither accepts site: "all", so a run across several sites is a series of single-site calls.

Kiro prompts before it runs an MCP tool unless a rule allows it, either in the server entry's autoApprove list or in a permission rule that matches xspeedhub/cloudflare_verify with effect allow. Both work per tool, which fits this job, because the three Cloudflare tools differ in risk: one reads, one clears a cache, and one slows the site for real visitors for hours. Allow the read and leave the other two on the prompt. In a workspace you have not trusted, Kiro asks before every MCP call even when autoApprove lists the tool. When Kiro prompts, read the site name in the call before you approve it, and ask the agent to turn development mode off in the same conversation once you have finished checking the page.

Set up Kiro once

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

Open the command palette and run Kiro: Open user MCP config (JSON), then add this entry. The user file applies in every workspace. A project can carry its own .kiro/settings/mcp.json instead, but Kiro does not load a workspace's MCP config until you trust that workspace. Kiro reconnects servers when you save the file.

~/.kiro/settings/mcp.json

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

3Approve access in the browser

After you save, Kiro opens the xSpeed Hub authorization page. It registers itself through dynamic client registration, so there is no client ID to create. Sign in to the Hub, approve, and check the MCP servers tab in the Kiro panel for a connected xspeedhub. There is no token to paste; Kiro keeps the credentials it receives.

1 / 3

Full Kiro 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. Kiro prompts before it runs an MCP tool unless a rule allows it. Rules live in two places: autoApprove in the server's mcp.json entry, which lists tool names, and mcp rules in permissions.yaml, such as a match of xspeedhub/get_* with effect allow. Allow the reads and keep purge_cache, update_settings, toggle_cache and the other write tools off both lists, because the Hub itself runs a write as soon as your connection allows it. Putting "*" in autoApprove skips the prompt for every Hub tool, writes included. In a workspace you have not trusted, Kiro asks before every MCP call even when autoApprove lists the tool.

What do I ask?

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

Prompt for Kiro

Use xSpeed Hub to verify the Cloudflare connection on shop. Do not purge or change anything.

Prompt for Kiro

With xSpeed Hub, purge the Cloudflare edge cache for blog and tell me what it returned.

Prompt for Kiro

Use xSpeed Hub to turn on Cloudflare development mode for shop for my debugging session, then remind me to switch it off.

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 Kiro

Put only cloudflare_verify in the autoApprove list for the xspeedhub server. Putting "*" there skips the prompt for every Hub tool, and so does adding set_cloudflare_dev_mode: the Hub does not prompt either, and a vague request can leave a live site in development mode, slower for real visitors, until it runs out after about three hours. Entries are per tool, so adding the read does not add the writes. If the agent should only report, list the two write tools in disabledTools and Kiro never offers them. Kiro's prompt shows the arguments, so read the handle before you approve, and ask for one site per request so each approval maps to one change.

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

Only cloudflare_verify, which reads and purges nothing. purge_cloudflare and set_cloudflare_dev_mode change what visitors see, and the Hub does not confirm them, so keep them on Kiro's prompt.

Yes. All three Cloudflare tools need Cloudflare connected in xSpeed on that site. Without it they return an error instead of changing anything. A passing cloudflare_verify does not prove development mode will work: a token without Zone Settings Edit verifies and purges, then fails when dev mode writes the setting.

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

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

Open xSpeed Hub Kiro setup

Manage Cloudflare caching with Kiro

How Kiro handles this

Set up Kiro 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 Kiro.