Warm the WordPress cache with Kimi Code

Warming the WordPress cache with Kimi Code means asking Moonshot AI's terminal agent, in the session you deployed from, to start the xSpeed preloader on a site through xSpeed Hub and read back how far the crawl has got.

list_sitesget_cache_statusget_settingsupdate_settingsstart_preloaderget_preloader_statusstop_preloader

Last updated: October 2026

Example session · Kimi Code

You: Deploy is done and shop is purged. Use xSpeed Hub to warm it.

get_preloader_status(site: shop) read-only
→ idle, no run in progress

Kimi Code: No crawl is running on shop. Start the preloader there? Kimi Code will ask you to approve the call.

You: Approve.

start_preloader(site: shop) changes site
→ Queued 402 URLs from the sitemap; pages are fetched in the background

Kimi Code: Started, 402 URLs queued. Ask me for the status whenever you want; that read runs without a prompt under your allow rule.

How Kimi Code handles this

The deploy just finished in your terminal and you purged the site from the same Kimi Code session. Now the cache is empty and the next visitors would build every page themselves. You ask Kimi Code to warm it. It calls get_preloader_status first, so it does not start a second crawl on top of a running one, then start_preloader, and prints the number of URLs the site queued from its sitemap.

The crawl runs inside WordPress, a few pages per run, so you can keep working while it goes. Ask again and Kimi Code reads get_preloader_status for the processed count, the last URL and recent errors. If the site refuses because the preloader module is off, the default on a fresh install, Kimi Code can read the module with get_settings and propose update_settings to switch it on. stop_preloader ends a crawl that is slowing the server, and pages already warmed stay cached. Each call prints under your deploy output, which makes the scrollback a record of what ran.

In the default Always Ask mode, an MCP call that matches no permission rule asks for approval, and Approve for this session lets the same kind of call through until the session ends. An allow rule for mcp__xspeedhub__get_* under [[permission.rules]] in config.toml lets the status read run quietly, while start_preloader, stop_preloader and update_settings keep asking. xSpeed Hub has no confirmation step of its own, and it treats the preloader as low-risk, so the Kimi Code prompt is the check you see before a crawl starts.

Set up Kimi Code once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Kimi Code 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 to mcp.json

Put this in ~/.kimi-code/mcp.json to use the Hub in every project, or in .kimi-code/mcp.json inside one repository, where it overrides a user entry of the same name. You can also run /mcp-config and let Kimi Code add it. A server added while a session is open joins only the next session.

~/.kimi-code/mcp.json

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

3Sign in with /mcp-config login

Start a new session with kimi, run this and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste. Then run /mcp to check that xspeedhub is connected.

Text

/mcp-config login xspeedhub
/mcp

1 / 3

Full Kimi Code 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. In Kimi Code's default Always Ask mode, an MCP call that matches no permission rule asks for approval, and Approve for this session allows the same kind of call until the session ends. Permanent rules go in [[permission.rules]] in config.toml: allow mcp__xspeedhub__get_* and mcp__xspeedhub__list_* to let the reads run, and leave the write tools on the prompt. Ask When Needed mode, from /yolo, approves MCP calls automatically, and Never Ask, from /auto, approves everything. xSpeed Hub has no confirmation step of its own, so in either of those modes a purge or a settings change runs as soon as your connection allows writes. To remove writes altogether, list the read tools in the entry's enabledTools, or use a connection token with Read-only everywhere on.

What do I ask?

Three prompts written for Kimi Code. More for this job are below.

Prompt for Kimi Code

I just deployed to shop. Use xSpeed Hub to check whether a crawl is running there, and start the preloader if not.

Prompt for Kimi Code

Using xSpeed Hub, how far through its crawl is blog? Show processed against total and any errors.

Prompt for Kimi Code

With xSpeed Hub, stop the preloader on docs. The server is busy with a migration.

What happens, step by step

The first visitor to an uncached page pays for building it. The preloader fixes that by visiting your pages first. Through xSpeed Hub an agent can start the crawl on one site or on every site in a workspace, watch how far it has got, and stop it. The crawl runs inside WordPress in the background; the agent only starts it, reads its progress and stops it.

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.

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.

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.

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.

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.

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 worth keeping

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 Kimi Code

Kimi Code works in sessions you start, so it warms when you ask. For repeat warming, use the preloader module's Schedule setting in WordPress, manual, hourly, daily or weekly. /yolo selects Ask When Needed, which approves MCP calls automatically, and /auto selects Never Ask, which approves everything, so in either mode a start, a stop or a settings change runs without a prompt. Approve for this session has a smaller version of the same effect for the rest of that session. If a project should only read crawls, list get_preloader_status and the other reads in enabledTools, or send a connection token with Read-only everywhere on through bearerTokenEnvVar, which makes the Hub refuse every write.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Use xSpeed Hub to start the preloader on shop and tell me how many URLs it queued.

Prompt

Using xSpeed Hub, how far through its crawl is blog? Show processed against total and any errors.

Prompt

With xSpeed Hub, purge the cache on docs, then warm it again.

Prompt

Use xSpeed Hub to start the preloader on every site in my workspace and tell me which ones refused.

Prompt

Use xSpeed Hub to stop the preloader on shop. It is slowing the server down.

Prompt

The preloader on shop says it is disabled. Use xSpeed Hub to turn the module on, then start the crawl.

Prompt

Using xSpeed Hub, which of my sites has no running crawl and a low hit ratio?

Frequently asked questions

Yes. With xSpeed Hub in mcp.json and signed in through /mcp-config login, ask it to warm the site you deployed. It checks get_preloader_status, calls start_preloader and prints how many URLs were queued.

Add an allow rule under permission rules in config.toml for the Hub's get_ tools, which Kimi Code names mcp__xspeedhub__ followed by the tool name. start_preloader and stop_preloader keep asking unless you approve them for the session or switch modes.

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.

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.

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.

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.

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.

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, from Kimi Code.

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

Open xSpeed Hub Kimi Code setup

Warm the WordPress cache with Kimi Code

How Kimi Code handles this

Set up Kimi Code once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Warm the cache, from Kimi Code.