# Grok + xSpeed: Manage WordPress Caching from a Chat

> Grok is xAI's AI assistant on grok.com, and with xSpeed Hub added as a custom MCP connector it can read cache status, purge, change settings and run speed tests on your WordPress sites from a chat. You enter one URL on the connectors page, sign in once, and ask about any site in your workspace.

Page: https://xspeedcache.com/agent/grok/
Last updated: October 2026

- One custom connector on grok.com, every site you connected to the Hub
- An OAuth sign-in on an xSpeed Hub page, with no key to paste
- Grok calls the Hub tools when your question is about your sites, so set read-only access deliberately

## How do I connect Grok to xSpeed?

### 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 as a custom connector

Go to grok.com/connectors, click New Connector and select Custom. Enter this as the MCP server URL and complete the authentication: approve access on the xSpeed Hub page that opens. Grok then reads the Hub's tools and makes them available in your conversations.

```
https://app.xspeedcache.com/xspeed/mcp
```

### 3. Ask a first question

Start a chat and ask something that names xSpeed Hub, so Grok reaches for the connector. A list of your sites with their cache status means the connection works.

```
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
```

### 4. Or have a team admin provision it (alternative)

On Grok Business and Enterprise, xAI says a team admin must first provision a connector in the cloud console before members can use it. Give the admin the same URL; each member then signs in to xSpeed Hub with their own account.

```
https://app.xspeedcache.com/xspeed/mcp
```

**Authentication:** OAuth sign-in. After you enter the URL, Grok takes you through the sign-in: approve access on an xSpeed Hub page and there is nothing to paste. xAI's documentation describes no header field for a custom connector, so the connection token is not part of this setup.

**Check it worked:** ask "Use xSpeed Hub to list my sites and tell me which ones have page caching turned off."

## Does Grok ask before it changes my site?

xAI's connector documentation describes no per-tool approval setting. It says Grok can use a connector's tools whenever your questions relate to that service. xSpeed Hub has no confirmation step of its own, so a purge or a settings change runs as soon as Grok calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, but that is an instruction, not a lock. If you want Grok to read and never change anything, sign in as a Viewer member of the workspace, which only ever gets read access. Otherwise read what Grok says it is about to do before you answer yes.

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.

## Example session

```
You: Use xSpeed Hub to check whether caching is doing its job on docs.
  → run_benchmark(site: docs) [read-only]: cached 92 ms, uncached 1,140 ms
  → get_cache_status(site: docs) [read-only]: page cache on, hit ratio 58% in the last 24h
  → get_preloader_status(site: docs) [read-only]: preloader idle, last run 12 days ago, 74 URLs not warmed
Agent: A cached page answers in about 92 ms against 1.1 s uncached, so the cache works when it is hit. Only 58% of requests hit it, and 74 pages are cold because the preloader has not run for 12 days. Start the preloader on docs?
You: Yes, start it.
  → start_preloader(site: docs) [changes site]: preloader started, 74 URLs queued
Agent: Started. Give it a few minutes, then ask me to check the hit ratio again.
```

## What is Grok?

Grok is xAI's AI assistant. You use it at grok.com, where it answers questions, searches and analyzes, and takes actions in external tools you connect to it.

Connectors are how Grok reaches those tools inside a conversation. xAI's documentation says connectors are available to all Grok users, and that for a service outside its catalog you can bring your own MCP server: on the connectors page you choose New Connector, then Custom, and enter the server URL. MCP, the Model Context Protocol, is the open standard that describes the server's tools to Grok. Adding xSpeed Hub that way gives Grok the Hub's caching tools for every site in your workspace.

The server has to be reachable over the public internet, which xSpeed Hub is, so nothing needs to run on your machine.

## Why use Grok with xSpeed?

- **No terminal, no config file**: You enter one URL on grok.com and approve access once. That suits site owners who would rather ask than open wp-admin on each site.
- **Ask about the whole fleet**: The Hub fronts every site you connected, so "which of my sites has the lowest hit ratio" is one question, answered from live cache data.
- **Measure before you change**: Grok can run the Hub's benchmark and read the preloader before it suggests a purge or a warm-up, so the advice comes with numbers.

## Good to know

- xAI describes no per-tool approval setting for connectors, and Grok can use a connector's tools whenever your question relates to it. For read-only use, sign in as a Viewer member of the workspace.
- On Grok Business and Enterprise a team admin has to provision the connector in the cloud console before members can add it.
- This page covers the Grok chat app on grok.com. xAI's terminal coding agent, Grok Build, is a separate client with its own setup.
- The sign-in has to finish in a browser, because the custom connector authenticates when you add it.

## Prompts to try

- Use xSpeed Hub to show the cache hit ratio for every site and flag anything under 70%.
- With xSpeed Hub, compare cached and uncached response time on shop and tell me what the gap means.
- Use xSpeed Hub to read the PageSpeed score history for blog and tell me whether mobile is trending up or down.
- With xSpeed Hub, check whether Redis is reachable on shop before you suggest turning on the object cache.
- Use xSpeed Hub to list the modules on docs and tell me which ones are off, without changing any.

## What can Grok do with xSpeed?

- [Purge the WordPress cache with Grok](https://xspeedcache.com/agent/grok/purge-cache/): 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](https://xspeedcache.com/agent/grok/troubleshoot-cache/): 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](https://xspeedcache.com/agent/grok/speed-scan/): 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](https://xspeedcache.com/agent/grok/pagespeed-tests/): 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](https://xspeedcache.com/agent/grok/optimize-site/): 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](https://xspeedcache.com/agent/grok/cache-settings/): 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](https://xspeedcache.com/agent/grok/preload-cache/): Fill the page cache before visitors arrive, for example right after a purge or a deploy.
- [Set up the Redis object cache with Grok](https://xspeedcache.com/agent/grok/object-cache/): Connect a site to Redis or Memcached so database results survive between requests.
- [Manage Cloudflare caching with Grok](https://xspeedcache.com/agent/grok/cloudflare/): 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](https://xspeedcache.com/agent/grok/fleet/): Run one action across all of your sites, or a chosen few, and read the result site by site.

## Which way should I connect?

| Surface | Endpoint | Reaches | Auth | Tools |
| --- | --- | --- | --- | --- |
| [xSpeed Hub MCP](https://xspeedcache.com/docs/hub-mcp/) | `https://app.xspeedcache.com/xspeed/mcp` | Every site in your workspace, one connection | OAuth sign-in in the browser, or a connection token in an Authorization header | 29 tools (16 read, 13 write), seven of them can act on every site at once |
| [xSpeed Cache Site MCP](https://xspeedcache.com/docs/mcp-server/) | `https://your-site.com/xspeed/mcp` | One WordPress site | OAuth sign-in by a site admin, or the site's own token in an Authorization header | The full per-site tool set plus run_command for the WP-CLI surface |
| [xSpeed Scan MCP](https://xspeedcache.com/docs/scan-mcp/) | `https://xspeedcache.com/scan/mcp` | Any public URL, read-only | None. No account. | 5 tools: run_speed_scan, get_speed_scan and three product-info tools |
| [WP-CLI](https://xspeedcache.com/docs/wp-cli-commands/) | `wp xspeed …` | The site whose server the agent has a shell on | Your server login | Every xSpeed command: cache, purge, preloader, objcache, cf, score, settings and more |

## Frequently asked questions

### How do I add xSpeed Hub to Grok?

Go to grok.com/connectors, click New Connector and select Custom. Enter https://app.xspeedcache.com/xspeed/mcp as the MCP server URL and complete the sign-in by approving access on the xSpeed Hub page. The Hub tools then show up in your Grok conversations.

### Do I need an API key?

No. You approve access on an xSpeed Hub page and Grok keeps the credentials it receives. xAI's documentation describes no header field for a custom connector, so the Hub's connection token is not used here.

### Will Grok change my site without asking?

It can. xAI describes no per-tool approval setting for connectors, and xSpeed Hub has no confirmation step of its own, so a write runs once Grok calls it and your connection allows writes. The Hub tells the agent to confirm the site and to ask before a write that touches every site, but that is an instruction. For read-only access, sign in as a Viewer member of the workspace.

### Can I use it on Grok Business or Enterprise?

Yes, once a team admin provisions the connector in the cloud console, which xAI says is required before members of the organization can use it. Each member then signs in to xSpeed Hub with their own account.

### Does my computer need to be reachable by Grok?

No. xAI only requires that the MCP server be reachable over the public internet, and xSpeed Hub is. Your sites connect to the Hub from their own dashboards.

### Is this the same as Grok Build?

No. This page covers the Grok chat app on grok.com. Grok Build is xAI's coding agent for the terminal and adds the Hub with its own command. Both reach the same xSpeed Hub endpoint.

### How do I disconnect Grok?

Remove the xSpeed Hub connector from grok.com/connectors. Rotating or disconnecting the Hub's connection token does not end this sign-in, because the connector uses OAuth, so remove it on the Grok side.

## Also works with

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

## Sources

- xAI Docs: Grok connectors: https://docs.x.ai/grok/connectors