How do I connect Grok Bot to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Grok Bot.
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.
4Or add it to a Team Bot from the Setup panel alternative
Only a Team Bot's owner can change its setup, and the change reaches every teammate. The owner adds the plugin from the Plugins card in the Bot's Setup panel, choosing a custom MCP server over remote HTTPS. Because the Hub uses OAuth, each teammate then signs in to xSpeed Hub with their own account.
https://app.xspeedcache.com/xspeed/mcp
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
You: Use @xspeedhub (xSpeed Hub) to find out why so many requests on shop miss the cache.
get_cache_status(site: shop) read-only
→ page cache on, hit ratio 44% in the last 24h
get_settings(site: shop, module: cache) read-only
→ cache_expiry 2 (hours), 3 excluded URLs
Grok Bot: Only 44% of requests hit the cache, and cached pages on shop expire after only 2 hours, so many of them are gone before the next visitor arrives. Raising the expiry to 24 hours changes shop's settings. Change it?
You: Yes, set it to 24 hours.
update_settings(site: shop, module: cache, values: { cache_expiry: 24 }) changes site
→ stored, cache expiry now 24 hours
Grok Bot: Done. Cached pages on shop now last 24 hours. Ask me tomorrow and I will compare the hit ratio.
Using it
Prompts to try in Grok Bot
Paste one as it is, or change the site name.
Use @xspeedhub (xSpeed Hub) to show the cache hit ratio for every site and flag anything under 70%.
With xSpeed Hub, purge the page cache on blog, then start the preloader and tell me how many URLs it queued.
Use xSpeed Hub to run a mobile PageSpeed test on shop and compare it with the stored score history.
With xSpeed Hub, check whether Redis is reachable on shop before you suggest the object cache.
Every Monday, use xSpeed Hub to list sites whose preloader has not run in a week. Report only.
What can Grok Bot do with xSpeed?
A guide for each job, written for Grok Bot.
Purge the WordPress cache with Grok Bot
Clear stale pages after a deploy, an edit or a plugin update, on one site or all of them.
Find out why WordPress pages are not cached with Grok Bot
Work out why a site misses the cache, serves slow pages or shows a low hit ratio, using read-only checks first.
Scan a website for speed problems with Grok Bot
Get a graded speed report with the fix for every failing check and a link you can share, for your own site or any public URL.
Run and track PageSpeed tests with Grok Bot
Read the PageSpeed scores a site already has, run a new test when something changed, and tell a Lighthouse score from a cache benchmark.
Raise a WordPress site's PageSpeed score with Grok Bot
Preview and apply xSpeed's recommended settings to a site, check the pages still work, and be told plainly what caching cannot fix.
Tune WordPress cache settings with Grok Bot
See which modules a site has, read their current settings, change them, and turn page caching on or off.
Warm the WordPress cache with Grok Bot
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Grok Bot
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Grok Bot
Check the Cloudflare connection, clear the edge cache and switch development mode on or off for a site.
Manage every WordPress site at once with Grok Bot
Run one action across all of your sites, or a chosen few, and read the result site by site.
Run a report-only cache check as a routine
A routine tells one Bot when to run a workflow. Ask the Bot in plain words when to run, what to check, where to report and what it must not do, and it creates the routine and shows its next run. Background routines run on the Bot's cloud computer while your laptop is closed. The Hub has no scheduler for agent prompts, so the timer is the Bot's. Nobody is there to approve a change during a run, and xAI notes that a Test run performs real work, including calls to connected tools, so word every routine as report only and keep Ask first rules on the Hub's write tools.
Every weekday at 8:00 AM, use @xspeedhub (xSpeed Hub) to read the cache status of every site. Post a short report here listing any site with page caching off or a hit ratio under 70%, and any site you could not reach. Report only: do not purge, toggle, change settings or run speed tests.
Trust and safety
Does Grok Bot ask before it changes my site?
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.
xSpeed Hub
xSpeed Hub has no confirmation step of its own. Read tools change nothing on your sites, with one exception to know about: contact_support sends an email to xSpeed support, and a read-only connection can still call it. A write tool (a purge, a settings change, a cache toggle, or a speed test that spends the shared allowance) runs as soon as your connection allows writes. Three things stand between a prompt and a change: your connection's scope, because a read-only connection refuses every write tool (the connection token has a Read-only everywhere switch, and a Viewer member only ever gets read access); your AI client's own tool-approval prompt; and the Hub's instructions to the agent, which tell it to confirm the target site and to ask once before a write that touches every site.
Good to know
- Always allow saves a rule for matching actions. On a Hub write tool that removes the only prompt, because the Hub has no confirmation step of its own. Use Ask first rules for writes.
- A routine's Test run performs real work, including calls to connected tools. Test with a report-only prompt.
- A personal plugin is account-wide. A Team Bot's plugins come from its owner's Setup panel, and only that owner can change them.
- xAI says Grok Bot inherits your team's Cursor connector policy, and a blocked connector shows as Disabled by team admin. On a team plan an admin may need to allow the Hub first.
Reference
What is Grok Bot?
Grok Bot is xAI's product for Bots you keep around: AI teammates with names, jobs and context that builds up over time. xAI's documentation says all your Bots share one persistent cloud computer with a browser, a filesystem and a terminal, which runs in Cursor's cloud, so work continues while your device is closed. It comes with paid individual Cursor plans, Cursor Teams, or a linked SuperGrok subscription.
Connectors are installed as plugins, and an installed connector is account-wide rather than tied to one Bot. A plugin can be a custom MCP server over remote HTTPS, which uses each person's sign-in when the server uses OAuth. MCP, the Model Context Protocol, is how that plugin describes xSpeed Hub's caching tools to the Bot: status, purge, settings, preloader, object cache, Cloudflare and speed tests, for every site in your workspace.
At a glance
- Made by
- xAI
- Type
- Always-on agent
- Connects with
- a custom remote HTTPS MCP server plugin, added from chat
- Sign-in
- OAuth sign-in
- Last checked
- October 2026
Why use Grok Bot with xSpeed?
Checks that happen while you are away
A routine runs on the Bot's cloud computer on a schedule and posts what it found: a site with caching off, a hit ratio that dropped, a preloader that stopped.
An approval prompt you can tune
Allow once, Always allow and Deny on each action, plus Ask first rules in Auto-review that win over automatic allows, so Hub writes can always stop for you.
Connect once for every Bot
A plugin added from your own chat is account-wide, so your other Bots can use xSpeed Hub without another setup. A Team Bot's owner can add it for the team instead.
How does Grok Bot compare with other AI clients?
Every client below reaches the same 29 Hub tools once connected. What differs is where it runs, how you add the server and how it signs in.
| Client | Made by | Type | How you connect it | Sign-in |
|---|---|---|---|---|
| Grok Bot | xAI | Always-on agent | a custom remote HTTPS MCP server plugin, added from chat | OAuth sign-in |
| Grok | xAI | Chat app | grok.com/connectors, New Connector, Custom | OAuth sign-in |
| Grok Build | xAI | Terminal | grok mcp add --transport http, then a browser sign-in | OAuth sign-in or connection token |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in |
Which way should I connect?
Grok Bot can use the Hub, one site's own MCP server, or the no-account Scan MCP. The Hub is the one most people want.
xSpeed Hub MCPMost people
https://app.xspeedcache.com/xspeed/mcp - Best for
- Most people. One URL in your AI client, every site behind it.
- Reaches
- Every site in your workspace, one connection
- Sign-in
- OAuth sign-in in the browser, or a connection token in an Authorization header
- Tools
- 29 tools (16 read, 13 write), seven of them can act on every site at once
xSpeed Cache Site MCP
https://your-site.com/xspeed/mcp - Best for
- A single site, or work the Hub does not expose, such as database cleanup.
- Reaches
- One WordPress site
- Sign-in
- OAuth sign-in by a site admin, or the site's own token in an Authorization header
- Tools
- The full per-site tool set plus run_command for the WP-CLI surface
xSpeed Scan MCP
https://xspeedcache.com/scan/mcp - Best for
- Grading a site you do not run, or trying xSpeed before you install anything.
- Reaches
- Any public URL, read-only
- Sign-in
- None. No account.
- Tools
- 5 tools: run_speed_scan, get_speed_scan and three product-info tools
WP-CLI
wp xspeed … - Best for
- Agents that already run commands on the server, such as Claude Code or Codex over SSH.
- Reaches
- The site whose server the agent has a shell on
- Sign-in
- Your server login
- Tools
- Every xSpeed command: cache, purge, preloader, objcache, cf, score, settings and more
Frequently asked questions
Also works with
Documentation
From the blog
- How to Let Claude or ChatGPT Manage Your WordPress Site Speed (via MCP)
- Connecting Claude to a WordPress Fleet in 2026: One of These Five Routes You May Already Be Paying For
- xSpeed Cache MCP vs WP Rocket MCP in 2026: One Connects Once, the Other Once Per Site
- 10 Best WordPress MCP Servers in 2026: 486 in the Directory, Four With More Than Ten Reviews