Manage every WordPress site at once with Windsurf

Managing every WordPress site at once with Windsurf means telling the editor agent to run an xSpeed Hub action across your whole workspace, then reading a separate result for every site.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · Windsurf

You: Using xSpeed Hub, which of my sites are not getting much out of the cache? Measure them all.

list_sites read-only
→ 6 sites in this workspace

run_benchmark(site: all) read-only
→ 6 of 6 benchmarked; five at least 5x faster cached, blog 310 ms cached against 340 ms uncached

Windsurf: Five sites show a clear gain. blog has a small gap (310 ms against 340 ms), so something may be bypassing its cache. I can check its cache status next.

How Windsurf handles this

Windsurf is now shipped as Devin Desktop, and the agent most people use there is the Devin Local agent, with Cascade as the earlier surface. Whichever you open, the job is the same. You maintain a handful or a few dozen WordPress sites, you have just changed something they share, and you ask the agent to purge, warm or benchmark all of them. It calls the matching xSpeed Hub tool with site set to "all", and the Hub runs the sites one after another with a one-second pause.

You get one result per site. A run where seven sites clear and one errors is reported as seven done and one failed, with the error text for the one, because the Hub judges a fan-out site by site. Only seven tools take "all": purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. Reading one site's settings or health still means naming the site, so the agent makes those calls one at a time.

The Devin Local agent prompts for approval before it calls any MCP tool by default, and you can allow 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. For a purge, toggle, settings change or preloader call on every site, the Hub tells the agent to confirm once, with the site count. It is an instruction, not a lock, and it does not name optimize_site. A read-only connection, meaning the connection token with Read-only everywhere on or a Viewer sign-in, is the control that stops writes whatever the editor does.

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.

Terminal

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.

Terminal

devin mcp login xspeedhub

1 / 3

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.

Prompt for Windsurf

With xSpeed Hub, run the cache benchmark on all my sites and flag any where cached is not clearly faster than uncached.

Prompt for Windsurf

Use xSpeed Hub to purge every site in my workspace and list the ones that did not clear.

Prompt for Windsurf

Ask xSpeed Hub to turn page caching back on for every site where it is off, and tell me the list before you do it.

What happens, step by step

If you run many WordPress sites, repeating one action on each is the slow part. Through xSpeed Hub, seven tools accept every site in a workspace, or a list of handles, in a single call. The Hub runs the sites one after another and returns a result for each, so a site that fails is named instead of hidden. Everything else in the Hub works on one site per call.

See what you can reach

list_sites returns each site's handle, URL, status and scopes. When you have more than one workspace, list_workspaces returns each one's handle, id, your role, its site count, which one is the default, and whether this connection can reach it.

Choose the scope of the call

The agent passes site: "all" for every site in one workspace, or an array of handles for exactly those sites. For a workspace other than the default it also passes the workspace argument. Omit workspace and the call acts on the default workspace.

Confirm once

Before a purge, toggle, settings change or preloader call that touches every site, the Hub tells the agent to say "this will touch all N sites" and wait for you, then make one call. That instruction does not name optimize_site, so for it your client's prompt is the gate. It is guidance to the agent, not a lock. It is one tool call, so one approval in your client covers every site in it.

Run it as one call

The Hub runs the sites one after another with a one-second pause between live calls, so a fleet purge is not a burst of traffic at your servers. Revoked sites are skipped from "all". Each site's action lands in the activity log as its own row.

Read the result per site

The reply is a summary of targets, succeeded and failed, plus one row per site with ok and either its data or its error. Some sites failing is a partial success. Only a run where every site failed comes back as an error.

Follow up on the failures

The agent reports which sites failed and why, then retries just those handles with an array. Tools that read one site, such as get_cache_status and get_health, do not fan out, so a fleet-wide check means one call per site.

Reference

Fan-out tools	purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site, run_benchmark
Selector	site: "all", or an array of handles
What all covers	Every site this connection can see in one workspace, minus revoked ones
Pacing	One after another, with a 1 second pause between live calls
Result	summary (targets, succeeded, failed) and a row per site: ok, then data or error
Partial failure	Reported per site; the call counts as an error only when every site failed
Workspace argument	Optional. Omit it for the default workspace; name one by its handle or id from list_workspaces
Reach	Fixed when you approve the connection; list_workspaces shows reachable: false for the rest
Not fan-out	get_health, get_cache_status and every other tool take one site per call
Slow tools	optimize_site takes up to 2 minutes per site; a target_score run is capped at 12 rounds per call
Read-only	The connection token with Read-only everywhere on, or a Viewer sign-in, refuses every fan-out write; run_benchmark works. An OAuth sign-in gets the scopes the client asks for
Hub daily pass	Re-verifies sites, snapshots cache status and hit ratio, reads stored reports, alerts by Slack webhook or email

Rules worth keeping

Confirm once, then call once. The Hub has no confirmation step of its own, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates that matter. The Hub's "this will touch all N sites" is an instruction to the agent for purge, toggle, settings and preloader calls, and it does not name optimize_site.
"all" is one workspace, never every workspace. To act in another workspace, name it. A write to a non-default workspace must name it, and an array of handles is looked up only in the workspace the call names.
Read every result per site. Treat some sites failing as a partial result, and never accept a blanket "done" from the agent.
Try a behaviour change on one site before you send it to the fleet. toggle_cache and update_settings on every site are one call, and each site checks values against its own settings, so a Pro setting can fail on a Free site.
optimize_site on many sites is slow, because each site can take up to two minutes inside one call. Use dry_run first, or name a short list of handles.
The Hub has no scheduler for agent prompts. Its own daily pass and alerts run without an agent, and an agent can only act when you send a prompt or your AI client runs one on a timer.

Good to know with Windsurf

Pay attention to which Windsurf surface you are in before you follow a setup guide. The Devin Local agent and the older Cascade add MCP servers in different ways, and Cascade caps the tools it will use at 100 across all servers, so a long list of other servers can leave less room than you expect. Allowing the whole xspeedhub server for good also allows its site: "all" writes, so allow single read tools instead. The fleet calls themselves do not change. Whichever agent you use, fan-out stops at one workspace, so name the client workspace when you manage more than one.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Use xSpeed Hub to list every site I can reach, and every workspace, and say which workspace you act in by default.

Prompt

With xSpeed Hub, purge the cache on every site in my workspace and tell me which ones failed.

Prompt

Use xSpeed Hub to run a benchmark on all my sites and rank them by cached response time.

Prompt

Use xSpeed Hub to start the preloader on blog, shop and docs only.

Prompt

With xSpeed Hub, turn page caching on for every site where it is off. Check each site first.

Prompt

Use xSpeed Hub to stop the preloader everywhere. The servers are busy.

Prompt

Ask xSpeed Hub to preview a safe optimize_site pass on every site with dry_run and summarize what it would change.

Prompt

Use xSpeed Hub to purge every site in the client-acme workspace, not my default one.

Frequently asked questions

It is shipped as Devin Desktop now, and the Devin Local agent is the main one to use, with Cascade as the earlier agent. The xSpeed Hub fleet tools behave the same in either, since both talk to the same MCP server.

Yes. run_benchmark accepts all and is a read tool, so it measures the cached and uncached response time on each site and changes nothing. It does not return a Lighthouse score.

Every site the connection can see in one workspace. It never crosses workspaces, and revoked sites are skipped. If your connection is limited to some sites, "all" quietly means the sites you are allowed, with no error naming the rest. To act in another workspace, the agent names it with the workspace argument.

The other sites still run. The reply has a summary and a row for each site with ok and its data or its error, so a site that was unreachable is named. A run counts as an error only when every site failed. Ask the agent to retry just the failed handles.

No. get_health and get_cache_status take one site per call, so the agent loops. The tools that fan out are purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. The Hub dashboard has a fleet overview for health.

Yes, on its own. A daily pass re-verifies each site, retrying a failed probe once, snapshots cache status and hit ratio, and reads the PageSpeed and GTmetrix reports your sites already stored. It can alert you by Slack webhook or email when a site becomes unreachable, caching is switched off, the hit ratio falls below a floor you set, or a score regresses. Each alert fires once per incident, not every day.

The Hub has no confirmation step. Its instructions tell the agent to confirm once with you, saying how many sites a call will touch, but that is guidance and not a lock. Your AI client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are what stop a write. The instruction covers purge, toggle, settings and preloader calls, not optimize_site. The dashboard's own Purge all button does confirm before it runs.

No. It cannot add, remove or rename sites, change members, roles or billing, mint or rotate tokens, or widen the workspaces this connection reaches. Those stay in the Hub dashboard.

Manage every site at once, from Windsurf.

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

Open xSpeed Hub Windsurf setup

Manage every WordPress site at once with Windsurf

How Windsurf handles this

Set up Windsurf 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 every site at once, from Windsurf.