Manage Cloudflare caching with Zed

Managing Cloudflare with Zed means asking its agent panel, in the editor where you write code, 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 · Zed

You: blog is showing an old sidebar to visitors. Use xSpeed Hub to check whether Cloudflare is the cause.

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

Zed: Cloudflare is connected on blog, so the edge may hold the old sidebar, and so may xSpeed's page cache on the server. Purge blog's page cache, then run purge_cloudflare?

You: Yes, both.

purge_cache(site: blog, type: page) changes site
→ page cache purged (44 entries)

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

Zed: The page cache and the edge cache are both purged for blog. Reload it logged out to see the current sidebar.

How Zed handles this

You are in Zed with the agent panel open, and the site you just updated still looks old when you load it outside your session. Ask the agent about Cloudflare for that site. It calls list_sites to find the handle, then cloudflare_verify to check whether the credentials and zone saved in xSpeed still resolve. The result appears in the panel beside your open files.

Next 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 origin changes show immediately. Both writes need Cloudflare connected in xSpeed on that site, and neither accepts site: "all", so each call names one site.

Zed's default tool permission is confirm, which asks before every tool action, MCP reads included. You will see a prompt even for cloudflare_verify, which changes nothing, and you read each Cloudflare call and its arguments before it runs. To quiet the read, add a per-tool entry, mcp:xspeedhub:cloudflare_verify, with a default of allow. The Always for tool button in the prompt writes the same entry. Zed documents only tool-level entries for MCP tools, with no wildcard, so you allow each read one at a time and the two writes stay on confirm. Setting the global default to allow would loosen every tool, not just xSpeed. After the chore, ask the agent to list the calls it made, so the thread records which site was touched and by which tool.

Set up Zed once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Zed 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 as a remote server

Open Settings, then AI, then MCP Servers, click Add Server and choose Add Remote Server. Or run zed: open settings file and add the entry yourself. Zed calls MCP servers context servers, so the key is context_servers.

settings.json

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

3Sign in

Because the entry has no Authorization header, Zed prompts you to authenticate against the server with the standard MCP OAuth flow. Approve access on the xSpeed Hub page that opens. There is no token to paste. Back in Settings, AI, MCP Servers, a green dot beside xspeedhub with the tooltip Server is active means it is connected.

Text

Settings → AI → MCP Servers

1 / 3

Full Zed 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. The Zed agent confirms before it runs any tool action. The default setting, agent.tool_permissions.default, is confirm, and that covers MCP tool calls, reads included. A per-tool entry such as mcp:xspeedhub:get_cache_status with a default of allow lets that one tool run without a prompt, and the Always for tool button in the prompt writes the same entry. Setting the global default to allow auto-approves every tool, writes included, and then a write reaches the Hub as soon as your connection allows writes. xSpeed Hub has no confirmation step of its own.

What do I ask?

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

Prompt for Zed

With xSpeed Hub, run a Cloudflare check on shop and tell me exactly what came back.

Prompt for Zed

Use xSpeed Hub to purge only the Cloudflare edge cache on blog.

Prompt for Zed

With xSpeed Hub, turn on Cloudflare development mode for shop while I debug the header, and keep a note to turn 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 Zed

Because Zed confirms every tool call by default, you will approve cloudflare_verify as well as the writes, and it is tempting to set the global default to allow just to stop that. Do not: that default covers every tool, so it would let set_cloudflare_dev_mode and purge_cloudflare run without a prompt, and the Hub adds none. Add a per-tool allow entry for cloudflare_verify instead, and keep the confirmation for the two Cloudflare writes. These settings apply to the native Zed agent. External agents and terminal threads follow their own configuration.

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

Zed's default tool permission is confirm, which prompts for every tool action, MCP reads included. The prompt is Zed's, not the Hub's. Add a per-tool entry such as mcp:xspeedhub:cloudflare_verify with a default of allow, and keep the confirmation for purge_cloudflare and set_cloudflare_dev_mode.

Not in one call. purge_cloudflare takes one site at a time. Ask the agent to go through your sites and it will call the tool once for each, with a confirmation prompt each time under Zed's default.

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

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

Open xSpeed Hub Zed setup

Manage Cloudflare caching with Zed

How Zed handles this

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