How Windsurf handles this
You are in Windsurf, now shipped as Devin Desktop, with a WordPress project open and the Devin Local agent in a tab. You edit a template, save, and want to see the change on the live site, so you tell the agent: purge the cache on shop. It calls list_sites to match the name, chooses a purge type from what you changed, and runs purge_cache. The call and its result appear in the agent thread.
The flow is quick because the agent sits next to your files. It can read what you touched, so for a stylesheet edit it can reason that assets is enough, and for a template edit that page is. What comes back is the plugin's report: the purge type, the site, how many entries cleared, and for all the object cache and a connected Cloudflare edge as well. Ask the agent to start the preloader and it queues the warm-up, then you can ask for the hit ratio a few minutes later.
Devin Local prompts before it calls any MCP tool, and in the prompt you can allow that one tool or the whole xspeedhub server, for this session or permanently. Smart mode lets a fast model run what it judges safe, and Bypass mode approves everything. xSpeed Hub has no confirmation of its own, so those settings and your connection scope are the gates. For a purge across every site the Hub also tells the agent to say that it will touch all the sites and wait for your yes.
Set up Windsurf once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Windsurf 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 for the Devin Local agent
Run this in a terminal. Devin Local shares its MCP configuration with Devin CLI, and -s user saves the server to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows) so it applies to every project. Without -s, the command saves to local scope, which is the current project only.
devin mcp add -s user xspeedhub https://app.xspeedcache.com/xspeed/mcp
3Sign in
Run the login command and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste, and the client keeps the credentials it receives. If the server later shows Needs auth in the Devin Local MCP list, click Authenticate, or run devin mcp logout and then login again.
devin mcp login xspeedhub
Full Windsurf 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 Devin Local agent prompts for approval before it calls any MCP tool. In the prompt you can allow that one tool or every tool on the xspeedhub server, for this session or permanently, and permission rules such as mcp__xspeedhub__get_cache_status allow, deny or always ask for a named tool. Smart mode lets a fast model run what it judges safe without a prompt, and Bypass mode approves everything, so with either of those 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 Windsurf. More for this job are below.
I edited the product template on shop. Use xSpeed Hub to purge the page cache there and tell me how many pages were cleared.
With xSpeed Hub, purge shop fully, start the preloader, and read the cache status when it finishes.
Ask xSpeed Hub to purge every site in my workspace and list any that failed.
What happens, step by step
A purge throws away stored copies so the next visitor gets a fresh page. Through xSpeed Hub an agent can purge everything, only pages, only CSS and JavaScript assets, the object cache or the REST cache, on one site or across every site in a workspace. A full purge also clears the Cloudflare edge when the site has Cloudflare connected.
01
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.
02
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.
03
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.
04
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.
05
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 worth keeping
- 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 Windsurf
Allowing the whole xspeedhub server in the prompt, or running Smart or Bypass mode, lets purge_cache run the moment the agent calls it. Allow single reads such as get_cache_status, add a rule that asks for mcp__xspeedhub__purge_cache, and approve writes one at a time. If you use the legacy Cascade agent instead, it can load at most 100 MCP tools across every server you have enabled, and the Hub's 29 count toward that, so turn other servers off if it cannot see purge_cache.
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
Keep going
Purge the cache with other agents
More with Windsurf
Documentation
- How to enable Page Cache
- How to warm your cache ahead of visitors
- Managing your fleet with xSpeed Hub
- How to write prompts for xSpeed Hub
- Windsurf + xSpeed
- Every AI agent that works with xSpeed
From the blog