# Warm the WordPress cache with Cursor

> Warming the WordPress cache with Cursor means asking its agent chat, inside the editor where you just changed the theme or plugin, to start the xSpeed preloader on the live site through xSpeed Hub.

Page: https://xspeedcache.com/agent/cursor/preload-cache/
Last updated: October 2026

You are in the editor, you have just pushed the theme change, and the live site has an empty cache. In the agent chat you write which site to warm. Cursor calls list_sites, picks the handle, and calls start_preloader. The plugin starts crawling the sitemap in the background, so visitors find stored pages instead of waiting for rebuilds.

The tool call shows up in the chat as its own step with its arguments, so you can read exactly which site it names before it runs. Ask for progress and the next step is get_preloader_status, which reports whether a run is active and how far through the URL list it has got. Asked to stop, Cursor calls stop_preloader. Pages already warmed stay cached, so a stop only ends the crawl.

Run Modes, under Settings > Agents > Approvals & Execution, decide whether Cursor asks before it uses an MCP tool. Since Cursor 3.6 the recommended default is Auto-review, which runs allowlisted calls at once and sends the rest to a classifier, and Cursor says it is not a security boundary. Allowlist runs only what you listed and asks about everything else. Run Everything asks nothing. xSpeed Hub has no confirmation of its own, so a tool you allowlist, a call a classifier lets through, or any call under Run Everything starts a crawl as soon as your connection allows writes. Because the chat sits beside your files, you can also ask Cursor to note in the pull request which pages were warmed after the release, using what get_preloader_status returned.

## Set up Cursor once

### 1. Put 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.

### 2. Add xSpeed Hub to mcp.json

Add the server to ~/.cursor/mcp.json to have it in every project, or to .cursor/mcp.json inside a project to scope it there. The entry is just a name and a url.

File: `~/.cursor/mcp.json`

```json
{
  "mcpServers": {
    "xspeedhub": {
      "url": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}
```

### 3. Enable it and sign in

Open Customize in the sidebar, find xspeedhub and make sure it is switched on. When Cursor starts the OAuth sign-in, approve access on the xSpeed Hub page. There is no token to paste. If the server shows an error, open the Output panel with Cmd+Shift+U and pick MCP Logs.

```
Customize  >  xspeedhub  (on)
```

Full setup: https://xspeedcache.com/agent/cursor/

### 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. Cursor decides how to treat an MCP tool call by its Run Mode, and you can expand a call to see its arguments. MCP follows the same Run Modes as terminal commands, set under Settings > Agents > Approvals & Execution. The recommended default, Auto-review, runs allowlisted calls at once and sends the rest to a classifier, not to you. Allowlist runs only what you listed, and with an empty list it asks you every time. Run Everything runs every tool call without asking. xSpeed Hub has no confirmation step of its own, so a tool you allowlist, or any call under Run Everything, writes as soon as your connection allows writes. Auto-review is a model, and Cursor says it is not a security boundary.

## Prompts

- I pushed the new header to production. Use xSpeed Hub to warm the shop site and show me the preloader status.
- Using xSpeed Hub, is a preload still running on blog? Check, and stop it if it is.
- With xSpeed Hub, warm all my sites, but list them first and confirm with me before you call anything.

## Example session

```
You: Header change is live. Use xSpeed Hub to warm the cache on shop.
  → start_preloader(site: shop) [changes site]: Queued 260 URLs from the sitemap; pages are fetched in the background
Agent: Started. I will check where it stands whenever you want.
You: Status?
  → get_preloader_status(site: shop) [read-only]: Running, 110 of 260 URLs warmed
Agent: 110 of 260 pages are warm and the crawl is still going. The crawl keeps going in the background.
```

## How it works

1. **Check the cache and the preloader**: get_cache_status tells the agent whether page caching is on, because there is nothing to fill when it is off. get_preloader_status shows whether a crawl is already running, so the agent does not start a second one.
2. **Make sure the preloader is switched on**: The preloader module is off on a fresh install, and the site refuses start_preloader until it is on. The agent can read the module with get_settings and, if you agree, switch it on with update_settings on the preloader module. The Hub tells the agent to briefly confirm intent before an update_settings call, but that is guidance to the agent, not a lock.
3. **Start the crawl**: start_preloader makes the site read its sitemap, follow any nested sitemap indexes, drop URLs that your cache exclusion rules skip, and queue the rest. The call returns once the queue is built; the pages are then fetched in the background, a few per run. For every site at once the agent passes site: "all", and the Hub starts the sites one after another with a one-second pause.
4. **Watch the progress**: get_preloader_status reports whether a crawl is running, how many URLs it has processed out of the total, the last URL it visited and the most recent errors. It works on one site at a time, so for several sites the agent calls it once per site.
5. **Read what failed**: A page that answers 403 or 406 usually means a server firewall is blocking the warmer by its user-agent, not that the page is broken. The status message names the user-agent to allow. A crawl that queues no URLs is reported as an error with the reason, not as a success.
6. **Stop it if the server struggles**: stop_preloader ends a running crawl. It is safe mid-run: pages already warmed stay cached. The agent can stop one site or every site in the workspace.

## Reference

| | |
| --- | --- |
| Start and stop | start_preloader and stop_preloader (write) |
| Progress | get_preloader_status (read): running or not, processed out of total, last URL, recent errors |
| What gets crawled | The sitemap (the WordPress one at /wp-sitemap.xml unless you set another), nested indexes followed, excluded URLs skipped |
| Needs | The preloader module switched on (it is off by default) and page caching on |
| Pages per run | 5 by default, 1 to 50, set in the preloader module |
| Schedule setting | manual, hourly, daily or weekly, set in the preloader module |
| Every site at once | start_preloader and stop_preloader accept site: "all"; get_preloader_status does not |
| Fan-out pacing | Sites start one after another with a 1 second pause, one result per site |
| Warmer user-agent | xSpeed-Warmer/1.0, the string a firewall rule would need to allow |
| Stopping | Safe mid-run; warmed pages stay cached |
| Read-only access | A Viewer member's sign-in, or the connection token with Read-only everywhere on: start_preloader and stop_preloader are refused; get_preloader_status works. An OAuth sign-in by anyone else gets the scopes the client asks for. |
| Confirmation | None on the Hub; your client's prompt is the gate |

## Rules

- Warm after a purge, not instead of one. The Hub tells the agent that starting the preloader after a purge saves the next visitor from paying for the rebuild.
- A crawl requests every page in the sitemap, so it adds load to the origin. Start with one site, and on a small host keep Pages per run low or stop the crawl if the site slows.
- start_preloader and stop_preloader are write tools. The Hub calls the preloader low-risk and only asks the agent to confirm when the target site is unclear or the call covers every site, so your client's approval prompt and read-only access (a Viewer sign-in, or the connection token with Read-only everywhere on) are the gates that matter.
- A fan-out only starts the crawls. Check each site with get_preloader_status afterwards, and treat some sites failing to start as a partial result, not a failure of the whole call.

## Good to know with Cursor

Switch Run Mode to Allowlist (Settings > Agents > Approvals & Execution), list get_preloader_status and leave start_preloader and stop_preloader off the list, so each one asks. Under the default Auto-review, unlisted calls go to a classifier that Cursor says can allow something you would have blocked, and under Run Everything the two preloader writes run silently, on any site the agent names, and the chat only shows them afterwards. Run Modes apply to local agents: Cursor says Cloud Agents never ask for approval, so give a Cloud Agent only a read-only Hub connection, meaning the connection token with Read-only everywhere on (or a Viewer sign-in). A refusal from a site whose preloader module is off appears as a failed tool step in the chat, not as a started crawl.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Use xSpeed Hub to start the preloader on shop and tell me how many URLs it queued.
- Using xSpeed Hub, how far through its crawl is blog? Show processed against total and any errors.
- With xSpeed Hub, purge the cache on docs, then warm it again.
- Use xSpeed Hub to start the preloader on every site in my workspace and tell me which ones refused.
- Use xSpeed Hub to stop the preloader on shop. It is slowing the server down.
- The preloader on shop says it is disabled. Use xSpeed Hub to turn the module on, then start the crawl.
- Using xSpeed Hub, which of my sites has no running crawl and a low hit ratio?

## Frequently asked questions

### Does Cursor ask me before it starts the preloader?

That depends on your Run Mode. Allowlist asks about every tool you have not listed. Under the default Auto-review since Cursor 3.6, a classifier decides calls that are not allowlisted, and Run Everything asks nothing. The Hub runs start_preloader as soon as your connection allows writes, so in Allowlist mode the Cursor prompt is the check.

### Can I warm the site from the editor right after saving a file?

The agent does it when you ask in the chat, not on save. After you push the change to the live site, write the request and Cursor calls start_preloader. Nothing in the editor starts a crawl by itself.

### Why does start_preloader say the preloader is disabled?

The preloader module is off by default on a new install, and the site refuses to start a crawl until it is on. The agent can switch it on with update_settings on the preloader module, or you can turn it on in the xSpeed Cache panel in wp-admin. Page caching also has to be on, because the crawl exists to fill that cache.

### What does the preloader actually warm?

It reads the site's sitemap, which is the WordPress one at /wp-sitemap.xml unless you set a different sitemap URL, follows nested sitemap indexes and skips any URL your cache exclusion rules leave out. If the sitemap cannot be read, the site falls back to a list built from its own content and says so. If nothing at all is queued, the call reports an error with the reason.

### Can I warm every site with one prompt?

Yes. The agent passes site: "all" to start_preloader and the Hub starts the crawl on every site in the workspace one after another, returning a result per site. The Hub tells the agent to confirm that with you once first. The call only starts the crawls, so progress is read afterwards with get_preloader_status, one site at a time.

### Will warming slow my site down?

A crawl fetches your own pages, a few per run, so it adds load while it runs. The Pages per run setting controls how many, from 1 to 50 with a default of 5. If a site struggles, stop_preloader ends the crawl and the pages already warmed stay cached.

### Why do some pages fail with HTTP 403 or 406?

Those codes are what bad-bot firewall rules usually answer with, and they mean the warmer was judged by its user-agent, not that the page is missing. The warmer identifies itself as xSpeed-Warmer/1.0. Allow that user-agent in the server rule, or change it with the xspeed_preloader_user_agent filter, and run the crawl again.

### Can the agent keep my cache warm on a schedule?

The preloader has its own Schedule setting in WordPress: manual, hourly, daily or weekly. An agent can change it with update_settings. The Hub itself has no scheduler for agent prompts, so a prompt only runs when you send it or when your AI client runs it on a timer.

## Warm the cache with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/preload-cache/) · [Claude](https://xspeedcache.com/agent/claude/preload-cache/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/preload-cache/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/preload-cache/) · [Codex](https://xspeedcache.com/agent/codex/preload-cache/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/preload-cache/) · [Windsurf](https://xspeedcache.com/agent/windsurf/preload-cache/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/preload-cache/) · [Antigravity](https://xspeedcache.com/agent/antigravity/preload-cache/) · [Zed](https://xspeedcache.com/agent/zed/preload-cache/) · [Kiro](https://xspeedcache.com/agent/kiro/preload-cache/) · [OpenCode](https://xspeedcache.com/agent/opencode/preload-cache/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/preload-cache/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/preload-cache/) · [Grok Build](https://xspeedcache.com/agent/grok-build/preload-cache/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/preload-cache/) · [Grok](https://xspeedcache.com/agent/grok/preload-cache/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/preload-cache/) · [Muse](https://xspeedcache.com/agent/muse/preload-cache/) · [Manus](https://xspeedcache.com/agent/manus/preload-cache/) · [Kimi Code](https://xspeedcache.com/agent/kimi/preload-cache/) · [Paperclip](https://xspeedcache.com/agent/paperclip/preload-cache/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/preload-cache/)

## More with Cursor

- [Purge the WordPress cache with Cursor](https://xspeedcache.com/agent/cursor/purge-cache/)
- [Find out why WordPress pages are not cached with Cursor](https://xspeedcache.com/agent/cursor/troubleshoot-cache/)
- [Scan a website for speed problems with Cursor](https://xspeedcache.com/agent/cursor/speed-scan/)
- [Run and track PageSpeed tests with Cursor](https://xspeedcache.com/agent/cursor/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Cursor](https://xspeedcache.com/agent/cursor/optimize-site/)
- [Tune WordPress cache settings with Cursor](https://xspeedcache.com/agent/cursor/cache-settings/)
- [Set up the Redis object cache with Cursor](https://xspeedcache.com/agent/cursor/object-cache/)
- [Manage Cloudflare caching with Cursor](https://xspeedcache.com/agent/cursor/cloudflare/)
- [Manage every WordPress site at once with Cursor](https://xspeedcache.com/agent/cursor/fleet/)

## Documentation

- How to warm your cache ahead of visitors: https://xspeedcache.com/docs/preloader/
- How to crawl your sitemap: https://xspeedcache.com/docs/crawl-now/
- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/
- Managing your fleet with xSpeed Hub: https://xspeedcache.com/docs/managing-your-fleet-with-xspeed-hub/