See every site at a glance
One view, every attached site — cache status, live hit ratio, and the controls to act, without logging into a single wp-admin.
Illustrative — your real fleet, statuses, and ratios appear once sites are attached.
Everything, across the fleet
Every action the plugin exposes locally, you can trigger remotely — for one site, a group, or all of them at once.
Purge caches
Clear one site or every site at once — instantly, without opening a single wp-admin.
Preload & warm
Rebuild the cache ahead of visitors after a deploy, so the first hit is already fast.
Run benchmarks
Measure real response times per site on demand and see the time actually saved.
Check health
Spot misconfigurations, low hit ratios, and missing headers across the whole fleet.
Toggle modules
Flip caching or optimization features remotely — one site, a group, or all of them.
Apply recommendations
Act on Pro’s suggestions in place — no logging into each dashboard to click the same fix.
Just ask. It acts on all of them.
Connect one assistant to the Hub and it reaches every attached site through the same MCP tools — purge, preload, benchmark, diagnose — in a single request.
- No per-site wiring — the Hub fans one connection out to all sites
- Read and write, scoped by the same per-site token
- Works in Claude, ChatGPT, or any MCP client
Connect in one click — or by hand
A site is always attached from the plugin, where you’ve proven you own it. Two ways to do it:
One-click connect
FastestClick Connect to Hub. The plugin sends you to app.xspeedcache.com to log in and approve, then drops you back in the plugin already attached. A one-time signed nonce proves the round-trip — nothing secret travels in the URL.
Paste your site token
ManualPrefer to wire it up by hand? The xSpeed Hub card shows this site’s URL and its connection token. Log in at app.xspeedcache.com, add a new site, and paste both in.
Either way, the Hub authenticates with the same per-site connection token the MCP Server already uses — no second secret is created.
Made for running more than one site
If a single wp-admin was ever enough, you wouldn’t need the Hub. It earns its place the moment there’s a second site.
One site, or all of them
The MCP Server drives a single site. The Hub is the account layer that drives many — using the very same credential.
A link you fully control
Attaching a site never hands over the keys. The Hub rides on the credential your site already issued — and you can cut it at any time.
Per-site token
Each site attaches with its own credential — not a master key to your account.
Revoke anytime
Disconnect from the plugin or the Hub; the link dies from either side.
No secrets in the URL
A one-time signed nonce proves the connect round-trip — nothing sensitive travels in the address bar.
Same credential as MCP
The Hub reuses the token the MCP Server already issued. No second secret is ever created.