How Grok Bot handles this
You run a WooCommerce store and you have given a Grok Bot a job description: look after the store's caching. A new theme added a customer account area, and you want a second line of defence so no account page can be stored and shown to the next visitor. You attach the xspeedhub plugin with @ and ask the Bot to check. It calls get_settings for the cache module on shop, reads the excluded URLs and cookies, and compares them with the store pages that should never be cached: cart, checkout and the account area.
What comes back is one gap and one proposal. Logged-in customers already skip the cache through the default cookie exclusions, but /my-account/ is not on the URL list, so a plugin that signs customers in some other way would have nothing stopping it. The Bot would add the path and keep the existing entries. The Hub tells the agent to briefly confirm intent before update_settings, and Grok Bot also stops the call when an action needs approval, with Allow once, Always allow or Deny. Pick Allow once. A wrong key or value refuses the whole call and nothing is stored, and credential fields are refused over the Hub, so a Cloudflare token or a Redis password stays in the xSpeed dashboard.
What differs in Grok Bot is that the Bot keeps the job. Its context builds up over time and it works on a persistent cloud computer, so you can ask it to create a routine that reads the exclusions every Monday and posts what changed, even with your laptop closed. A routine runs unattended, and xAI notes that a Test run performs real work, including calls to connected tools. Set Auto-review rules under Settings, General, Auto-review that force Ask first for update_settings and toggle_cache, because Ask first wins over an automatic allow, and word every routine as report only.
Set up Grok Bot once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Grok Bot 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.
2Ask your Bot to add xSpeed Hub
In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.
3Attach it and ask a first question
Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
Full Grok Bot 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. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.
What do I ask?
Three prompts written for Grok Bot. More for this job are below.
Use @xspeedhub (xSpeed Hub) to check that cart, checkout and my-account are excluded from the cache on shop.
Every Monday, use xSpeed Hub to read the cache exclusions on shop and post what changed. Report only.
With xSpeed Hub, read the cache expiry on shop and tell me whether it suits a store that changes prices daily.
What happens, step by step
Every xSpeed feature is a module with its own settings. Through xSpeed Hub an agent can list the modules a site has, read one module's settings, change them with a checked update, and turn page caching on or off. The site validates every write against the module's own schema, so a wrong key or value is refused with a reason instead of being quietly ignored.
01
List the modules
list_modules returns every Free and Pro module available on one site, with its settings schema and status. It tells the agent which module slugs exist, such as minify or gzip, and what each setting accepts.
02
Read the current settings
get_settings takes a module slug and returns its settings. Credential fields come back masked, so an agent cannot read a stored API token or password back in plain text.
03
Change them
update_settings takes the module and a values object of setting keys. The site checks the whole object first. If any key is unknown, any value is outside the schema, or a field is pinned by a constant in wp-config.php, it refuses the write, writes nothing and says which keys and why, sometimes with a "did you mean" hint.
04
Turn page caching on or off
Page caching has its own tool, toggle_cache, because it installs or removes the cache drop-in and the WP_CACHE constant. Asking update_settings to set cache_enabled does not work and is refused. If another caching plugin owns the drop-in, the site declines to enable xSpeed and returns blocked: true with the reason.
05
Check the effect
The result of a settings write is the stored settings. A module can add a warning when a setting is saved but has no effect on this server, for example Brotli on a server without the module for it, and the agent should pass that on. run_benchmark then times cached against uncached to see whether the change helped.
06
Apply to many sites only after reading one
update_settings and toggle_cache accept site: "all" or a list of handles. Each site validates against its own schema and answers in its own row, so a module missing on one site fails that row and the others still apply. Read one site first, then apply.
Reference
| Discover | list_modules (read): Free and Pro modules, settings schema, status, per site |
|---|---|
| Read settings | get_settings (read): argument module; credential fields masked |
| Change settings | update_settings (write): arguments module and values; validated by the site |
| Bad input | The whole write is refused and nothing is written; the error names the keys and reasons |
| Page cache on or off | toggle_cache (write): argument enabled; cache_enabled in update_settings is refused |
| Blocked by another plugin | toggle_cache returns blocked: true with blocked_reason when another plugin owns the cache drop-in |
| Every site at once | update_settings and toggle_cache accept site: "all" or a list of handles, one result per site |
| Pro modules | A Pro module on a site without an active licence cannot be read or written; the site refuses |
| Credential fields | Refused by default over MCP; set them in the xSpeed dashboard, not through the agent |
| Read-only connection | The connection token with Read-only everywhere on, or a Viewer member's sign-in: update_settings and toggle_cache are refused; list_modules and get_settings still work. An OAuth sign-in gets the scopes the client asks for, read and write by default, clamped to the member's role |
| Confirmation | None on the Hub; the Hub tells the agent to briefly confirm intent for these two, and your client's prompt is the gate |
Rules worth keeping
- Read before you write. Ask for list_modules and get_settings first, so the agent changes real keys with valid values instead of guessing.
- update_settings and toggle_cache change how a live site behaves. They run as soon as your connection allows writes. The Hub tells the agent to briefly confirm intent first, which is guidance to the agent, 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. The switch does not limit an OAuth sign-in.
- For site: "all", the Hub tells the agent to confirm once with "this will touch all N sites", then make one call. The result is per site, and some sites failing is a partial result to report, not a blanket success or failure.
- Do not ask an agent to set credentials such as a Cloudflare token or Redis password. The site refuses those writes by default, and they belong in the xSpeed dashboard.
- If a settings result says a value is saved but inactive on this server, relay that. Do not tell the user the feature is enabled.
Good to know with Grok Bot
Always allow saves a rule, and on update_settings or toggle_cache it removes the only prompt, because xSpeed Hub has no confirmation step of its own: the next settings change runs as soon as the Bot decides to make it. Keep writes on Allow once or behind an Ask first rule. On a team plan, Grok Bot inherits your Cursor connector policy, so an admin may have to allow the plugin first, and only a Team Bot's owner can add it from the Setup panel. For a Bot that should only report, sign in as a Viewer member.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to list the modules on shop and tell me which ones are off.
Ask xSpeed Hub for the current minify settings on blog.
With xSpeed Hub, turn on HTML minification on blog, then benchmark the cache and tell me if it helped.
Use xSpeed Hub to turn page caching off on staging while I debug, and tell me when it is off.
Using xSpeed Hub, read the gzip settings on shop first, then enable the same options on every site.
Use xSpeed Hub to set the page cache lifespan on docs to 30 days, and if the site refuses it, tell me why.
Frequently asked questions
Keep going
Tune cache settings with other agents
More with Grok Bot
Documentation
- How to enable Page Cache
- How to minify CSS and JavaScript
- How to add cache rules and bypasses
- Site MCP tool reference
- How to write prompts for xSpeed Hub
- Grok Bot + xSpeed
- Every AI agent that works with xSpeed
From the blog