How Windsurf handles this
You are in Windsurf and the 24-hour hit ratio on the dashboard says 9%. That reads like a broken cache. You ask the agent: the hit ratio on blog is 9%, is caching actually failing? It lists your sites, reads get_cache_status and get_health, then runs run_benchmark.
The benchmark answers the real question. It times the home page cached and uncached, and reports whether the cached request was a hit. Here it was, at a fraction of the uncached time, and the health checks pass. The ratio is low because xSpeed counts requests that reach your server, so a CDN or Cloudflare answering at the edge keeps them out of the count. Visitors get the faster result; the figure just cannot see it. The agent explains that and asks about your setup instead of telling you to change settings.
Windsurf now ships as Devin Desktop, and its Devin Local agent prompts before it calls any MCP tool. You can allow one tool or the whole xspeedhub server, for this session or permanently. For this job that means a handful of read approvals and no change to your site. One follow-up is worth asking: what would be different if the ratio were wrong. If run_benchmark had shown that the cached request was not a hit, the cause would be on the server side, and the agent would go to get_health for the failing check. The same tools handle both cases, and only the second needs you to act. Keep that order in mind: benchmark first, ratio second.
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.
The hit ratio on blog is 9%. Use xSpeed Hub to run the benchmark and tell me whether caching is really failing.
Using xSpeed Hub, could my low hit ratio be a Cloudflare or CDN counting issue? Check before you suggest any change.
With xSpeed Hub, read get_health on blog and list every warning, with what each one means.
What happens, step by step
When a WordPress page is not served from cache, the cause is usually one of a few things: caching is off, the cache drop-in or the WP_CACHE constant is missing, another caching plugin is in the way, or the pages carry something that makes them uncacheable. Through xSpeed Hub an agent can read the cache status, run the site's full health diagnostics, time a cached request against an uncached one, and check which Pro features would help, all without changing anything.
01
Start with the quick summary
get_cache_status returns whether page caching is on, the stats (cached pages, size, hit ratio, last purge) and the web server xSpeed detected. It is a glance. If caching is off, or the hit ratio is far below what you expect, the agent moves on to the diagnostic.
02
Run the diagnostic
get_health is the tool for troubleshooting. It returns the environment checks with pass or warn tones (the advanced-cache.php drop-in, the WP_CACHE constant, rewrite rules, PHP and WordPress versions, caching plugin conflicts), the cache stats, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use it, not get_cache_status, when you are troubleshooting rather than glancing.
03
Time cached against uncached
run_benchmark requests the home page once with the cache bypassed and once normally, after a warm-up request, and returns the timings. If the second request still is not a cache hit, the page cache is not serving the home page, and the result says so. It measures xSpeed's own response time. It does not return a Lighthouse score.
04
Read what the checks mean
A warn is a lead, not always a fault. A static-file rewrite warning, for example, can mean the nginx snippet is not in your server config yet, or that xSpeed could not verify it, which is not evidence the config is wrong. The agent reads the detail line and tells you which one it is.
05
Fix it or hand it over
If caching is simply off, toggle_cache turns it on. If another caching plugin owns the drop-in, the site refuses to enable xSpeed and says why; removing the other plugin is yours to do. If nothing explains it, contact_support emails xSpeed support with the agent's summary, after the agent has confirmed the message with you.
Reference
| Quick check | get_cache_status (read): cache on or off, stats, detected web server |
|---|---|
| Diagnostic | get_health (read): environment checks, 24 hourly buckets, 30-day hit-ratio series, recent activity |
| One site per call | get_health does not accept site: "all"; call it for each site you care about |
| Benchmark | run_benchmark (read): home page only, cache bypassed against cache served, timings in milliseconds |
| Benchmark on every site | run_benchmark accepts site: "all" or a list of handles, one result per site |
| Benchmark history | get_benchmark_history reads past runs and the settings changes on the same timeline |
| Pro suggestions | get_pro_audit (read): which Pro features would help this site, from its settings and stats |
| Hit ratio scope | Counts requests that reach your server; pages answered by a CDN or Cloudflare edge are not counted |
| Support | contact_support emails xSpeed support with your account email and site list attached; classed read |
| Turning caching on | toggle_cache (write); refused by the site when another plugin owns the cache drop-in |
Rules worth keeping
- Diagnose with the read tools first. get_cache_status, get_health, run_benchmark and get_pro_audit change nothing on the site, so a read-only connection can run all of them. For clients that send the connection token, that means Read-only everywhere on; an OAuth sign-in gets the scopes the client asks for, unless the member is a Viewer.
- Do not answer a PageSpeed question with run_benchmark. It measures cached against uncached response time and returns no Lighthouse score; for a score, use the speed test or scan jobs.
- toggle_cache is a write. It runs as soon as your connection allows writes, and the Hub tells the agent to confirm the target site first. That is guidance to the agent, so your client's approval prompt is the gate that matters.
- contact_support sends a real email. The Hub tells the agent to confirm the message with you before sending, but the tool is classed read, so even a read-only connection can send one.
- The agent cannot edit your server configuration or another plugin's settings. When a check needs an nginx snippet or a conflicting plugin removed, it tells you what to do and you do it.
Good to know with Windsurf
Cascade, the older Windsurf agent, loads tools from every MCP server you enabled and caps them at 100 across all of them. xSpeed Hub contributes 29. If the agent says it cannot find get_health, other servers may be using up the cap, so turn off the ones you do not need for this task. And keep the ratio in proportion: behind a CDN, trust run_benchmark for whether caching works and the ratio only as a trend.
More prompts for this job
They work in any client connected to xSpeed Hub.
Using xSpeed Hub, why is the cache hit ratio so low on shop? Run the full health check and tell me the most likely cause.
Using xSpeed Hub, is page caching actually working on blog? Benchmark cached against uncached and tell me if the second request was a hit.
xSpeed Hub's get_health on docs shows a warning about the static-file rewrite. What does it mean and do I need to act?
Use xSpeed Hub to check whether another caching plugin is conflicting with xSpeed on shop.
Caching looks off on the staging site. Use xSpeed Hub to turn it on and tell me if the site refuses.
Using xSpeed Hub, which Pro features would help the shop site, based on how it is set up now?
With xSpeed Hub, compare the last few benchmark runs on blog and tell me whether my settings changes helped.
Frequently asked questions
Keep going
Find out why pages are not cached with other agents
More with Windsurf
Documentation
- How to read your cache diagnostics
- Understanding cache hits and misses
- How to check your site health
- Common problems and troubleshooting
- How to enable Page Cache
- How to write prompts for xSpeed Hub
- Windsurf + xSpeed
- Every AI agent that works with xSpeed
From the blog