Manage every WordPress site at once with Zed

Managing every WordPress site at once with Zed means asking its agent for one xSpeed Hub action across your whole workspace, approving the call, and reading a result for each site.

list_siteslist_workspacespurge_cachetoggle_cacheupdate_settingsstart_preloaderstop_preloaderoptimize_siterun_benchmark

Last updated: October 2026

Example session · Zed

You: Use xSpeed Hub to stop all the preloaders, the hosts are struggling.

list_sites read-only
→ 7 sites in the workspace

Zed: This will touch all 7 sites by stopping the preloader on each. Run it?

You: Yes, run it.

stop_preloader(site: all) changes site
→ 7 of 7 stopped

get_preloader_status(site: blog) read-only
→ idle

Zed: All seven preloaders are stopped. I spot-checked blog and it is idle. Stopping the preloader purges nothing, so pages already warmed stay cached.

How Zed handles this

You keep Zed open because it is fast, and the sites you look after share enough code that one change affects all of them. You ask the agent to purge every site and warm them again. It calls purge_cache with site set to "all" and then start_preloader the same way, on the xSpeed Hub server you added under context servers. The Hub runs the sites in order, a second apart, and sends back a result for each.

What you read afterwards is a per-site list: which sites purged, which did not, and the error for each that failed. Eleven out of twelve is reported as a partial success with the odd site named. Seven tools accept "all": purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. For anything else, such as get_health, the agent names a site and calls it again per site.

Zed's default tool permission is confirm, which means the agent prompts for every tool call, reads included. For fleet work this suits you well, because you see the exact arguments, site: "all" among them, before anything runs. For a purge, toggle, settings change or preloader call, the Hub also tells the agent to confirm once with the site count, but it does not name optimize_site. Treat the Zed prompt as the check, and a read-only connection token (Read-only everywhere on) or a Viewer sign-in as the stop that cannot be talked around.

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

Use xSpeed Hub to purge every site in the workspace and tell me which ones failed.

Prompt for Zed

With xSpeed Hub, run the benchmark on all of my sites, one table, slowest uncached first.

Prompt for Zed

Ask xSpeed Hub to stop the preloader on all sites, then confirm each one reports idle.

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 Zed

With the default confirm setting, Zed prompts for list_sites and every other read as well, so a fleet task that touches many sites one by one can mean many prompts. It is tempting to loosen the permission for xSpeed to cut that down. If you do, loosen it for the read tools only, because a looser rule on purge_cache or toggle_cache covers the site: "all" form too, and then the all-sites call runs without the prompt that currently protects you. Zed takes per-tool entries for MCP tools and no wildcard, so you list each read tool you want to allow, and the Always for tool button adds them one at a time. Setting the global default to allow auto-approves every tool. These settings apply to Zed's own agent. A better trade is to ask for run_benchmark when you want a fleet-wide picture, since one prompt covers every site.

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

With the default setting, yes. Zed asks for every tool call, and the prompt shows the tool and its arguments, so you can see that site is set to all before you approve.

Only seven tools accept all. For the rest, such as get_health, the agent makes one call per site, and Zed prompts for each call by default. Use the fan-out read tool run_benchmark where it fits, which covers every site in one prompt.

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 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 every WordPress site at once 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 every site at once, from Zed.