# AI Agents for WordPress Caching: Connect Any Agent | xSpeed

> AI agent WordPress caching means an AI agent such as Claude Code, ChatGPT, Cursor or Gemini CLI checks, purges, tunes and speed-tests the cache on your WordPress sites for you. xSpeed makes that work through xSpeed Hub: one MCP endpoint for every site you connect, which forwards each tool call to the xSpeed Cache plugin on the site you named.

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

## Which AI agents work with xSpeed?

| Agent | Made by | Type | How it connects | Auth | Guide |
| --- | --- | --- | --- | --- | --- |
| Claude Code | Anthropic | Terminal | claude mcp add, then /mcp to sign in | OAuth sign-in or connection token | https://xspeedcache.com/agent/claude-code/ |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token | https://xspeedcache.com/agent/claude/ |
| Claude Cowork | Anthropic | Desktop agent | A custom connector added to your Claude account | OAuth sign-in | https://xspeedcache.com/agent/claude-cowork/ |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in | https://xspeedcache.com/agent/chatgpt/ |
| Codex | OpenAI | Terminal | codex mcp add --url, then codex mcp login | OAuth sign-in or connection token | https://xspeedcache.com/agent/codex/ |
| Cursor | Anysphere | Editor | mcp.json with a url, then OAuth | OAuth sign-in or connection token | https://xspeedcache.com/agent/cursor/ |
| GitHub Copilot in VS Code | GitHub / Microsoft | Editor | mcp.json in your VS Code user profile, or MCP: Add Server | OAuth sign-in or connection token | https://xspeedcache.com/agent/github-copilot/ |
| Windsurf | Cognition | Editor | devin mcp add, then devin mcp login (Cascade: mcp_config.json) | OAuth sign-in or connection token | https://xspeedcache.com/agent/windsurf/ |
| Gemini CLI | Google | Terminal | gemini mcp add, then /mcp auth xspeedhub | OAuth sign-in or connection token | https://xspeedcache.com/agent/gemini-cli/ |
| Antigravity | Google | Editor | mcp_config.json with serverUrl, then Authenticate in settings | OAuth sign-in or connection token | https://xspeedcache.com/agent/antigravity/ |
| Zed | Zed Industries | Editor | context_servers in settings.json, or Settings, AI, MCP Servers | OAuth sign-in or connection token | https://xspeedcache.com/agent/zed/ |
| Kiro | Amazon (AWS) | Editor | an mcp.json entry with a url, then a browser sign-in | OAuth sign-in or connection token | https://xspeedcache.com/agent/kiro/ |
| OpenCode | SST | Terminal | a remote mcp entry in the config, then opencode mcp auth | OAuth sign-in or connection token | https://xspeedcache.com/agent/opencode/ |
| OpenClaw | Open source | Always-on agent | openclaw mcp add with --auth oauth, then openclaw mcp login | OAuth sign-in or connection token | https://xspeedcache.com/agent/openclaw/ |
| Hermes Agent | Nous Research | Always-on agent | an mcp_servers entry in config.yaml, then hermes mcp login | OAuth sign-in or connection token | https://xspeedcache.com/agent/hermes-agent/ |
| Grok Build | xAI | Terminal | grok mcp add --transport http, then a browser sign-in | OAuth sign-in or connection token | https://xspeedcache.com/agent/grok-build/ |
| ChatGPT dots | OpenAI | Always-on agent | the xspeedhub app from ChatGPT developer mode, shared through Plugins | OAuth sign-in | https://xspeedcache.com/agent/chatgpt-dots/ |
| Grok | xAI | Chat app | grok.com/connectors, New Connector, Custom | OAuth sign-in | https://xspeedcache.com/agent/grok/ |
| Grok Bot | xAI | Always-on agent | a custom remote HTTPS MCP server plugin, added from chat | OAuth sign-in | https://xspeedcache.com/agent/grok-bot/ |
| Muse | Meta | Chat app | a custom connector that Muse creates when you ask for it | Connection token | https://xspeedcache.com/agent/muse/ |
| Manus | Manus | Always-on agent | Settings, Integrations, Custom MCP Servers, Add Server | Connection token | https://xspeedcache.com/agent/manus/ |
| Kimi Code | Moonshot AI | Terminal | an mcpServers entry in mcp.json, then /mcp-config login | OAuth sign-in or connection token | https://xspeedcache.com/agent/kimi/ |
| Paperclip | Paperclip | Always-on agent | claude mcp add on the agent's host, or Connect your own MCP server | OAuth sign-in or connection token | https://xspeedcache.com/agent/paperclip/ |
| NanoClaw | NanoClaw | Always-on agent | ncl groups config add-mcp-server, then ncl groups restart | Connection token | https://xspeedcache.com/agent/nanoclaw/ |

## How do AI agents connect to xSpeed?

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

## How do I connect an AI agent 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.

```
# In each site's wp-admin
xSpeed Cache → Connect Hub → Connect via xSpeed Hub
```

### 2. Add one URL to your AI client

Every client on this page takes the same endpoint. Clients that sign in by URL open a browser page where you approve access. Clients that take headers can use the connection token from the Hub's Connect AI page instead.

```
# OAuth: paste the URL, approve in the browser
https://app.xspeedcache.com/xspeed/mcp

# Or with the connection token (Hub → Connect AI)
Authorization: Bearer <your connection token>
```

### 3. Decide what the agent may change

xSpeed Hub has no confirmation step of its own, so set this before your first request. Keep write tools on your client's approval prompt (each agent guide shows how), or connect read-only: the connection token with Read-only everywhere on, or a Viewer sign-in. A read-only connection can still call contact_support, which emails xSpeed support.

### 4. Ask for what you want

Name the site, or ask about every site. The agent lists your sites first, then calls the tools it needs and reports what came back.

```
You: Which of my sites has the lowest cache hit ratio?
     Purge that one and warm it again.

Agent: list_sites → 6 sites
       get_cache_status × 6 → shop: 41% hit ratio
       Purge and re-warm shop? (yes)
       purge_cache shop · start_preloader shop
```

## What can an AI agent do with xSpeed?

- **Purge the cache**: Clear stale pages after a deploy, an edit or a plugin update, on one site or all of them. Tools: list_sites, get_cache_status, purge_cache, purge_cloudflare, start_preloader. Example guide: https://xspeedcache.com/agent/claude-code/purge-cache/
- **Find out why pages are not cached**: Work out why a site misses the cache, serves slow pages or shows a low hit ratio, using read-only checks first. Tools: list_sites, get_cache_status, get_health, run_benchmark, get_benchmark_history, get_pro_audit, toggle_cache, contact_support. Example guide: https://xspeedcache.com/agent/claude-code/troubleshoot-cache/
- **Scan a site's speed**: 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. Tools: list_sites, get_speed_scan, run_speed_scan. Example guide: https://xspeedcache.com/agent/claude-code/speed-scan/
- **Track PageSpeed scores**: Read the PageSpeed scores a site already has, run a new test when something changed, and tell a Lighthouse score from a cache benchmark. Tools: list_sites, get_score_history, run_speed_test, get_benchmark_history, run_benchmark. Example guide: https://xspeedcache.com/agent/claude-code/pagespeed-tests/
- **Raise the PageSpeed score**: Preview and apply xSpeed's recommended settings to a site, check the pages still work, and be told plainly what caching cannot fix. Tools: list_sites, get_score_history, list_modules, optimize_site, generate_critical_css, purge_cache, run_speed_test. Example guide: https://xspeedcache.com/agent/claude-code/optimize-site/
- **Tune cache settings**: See which modules a site has, read their current settings, change them, and turn page caching on or off. Tools: list_sites, get_cache_status, list_modules, get_settings, update_settings, toggle_cache, run_benchmark. Example guide: https://xspeedcache.com/agent/claude-code/cache-settings/
- **Warm the cache**: Fill the page cache before visitors arrive, for example right after a purge or a deploy. Tools: list_sites, get_cache_status, get_settings, update_settings, start_preloader, get_preloader_status, stop_preloader. Example guide: https://xspeedcache.com/agent/claude-code/preload-cache/
- **Set up Redis object cache**: Connect a site to Redis or Memcached so database results survive between requests. Tools: get_object_cache_status, test_object_cache, get_settings, update_settings, toggle_object_cache, flush_object_cache. Example guide: https://xspeedcache.com/agent/claude-code/object-cache/
- **Manage Cloudflare**: Check the Cloudflare connection, clear the edge cache and switch development mode on or off for a site. Tools: cloudflare_verify, purge_cloudflare, set_cloudflare_dev_mode, purge_cache, get_settings. Example guide: https://xspeedcache.com/agent/claude-code/cloudflare/
- **Manage every site at once**: Run one action across all of your sites, or a chosen few, and read the result site by site. Tools: list_sites, list_workspaces, purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site, run_benchmark. Example guide: https://xspeedcache.com/agent/claude-code/fleet/

## The 29 xSpeed Hub tools

| Tool | Kind | What it does |
| --- | --- | --- |
| `list_sites` | read | List the sites this connection can reach, with their handles and status. |
| `list_workspaces` | read | List your workspaces and which ones this connection reaches. |
| `contact_support` | read (sends an email) | Email xSpeed support on your behalf, with your account email and site list. The Hub classes it read because it changes no site, so a read-only connection can still send it. |
| `get_cache_status` | read | Cache on or off, stats and server details for a site. |
| `list_modules` | read | Free and Pro modules, their settings schema and status. |
| `get_settings` | read | Current settings for one module. |
| `get_health` | read | Full diagnostics for one site. |
| `get_pro_audit` | read | Which Pro features would help this site. |
| `get_benchmark_history` | read | Past cached versus uncached response-time runs. |
| `get_score_history` | read | Stored PageSpeed and GTmetrix history. Starts nothing. |
| `get_preloader_status` | read | Where the cache preloader is and what it has warmed. |
| `get_object_cache_status` | read | Redis or Memcached status, or the wp-config snippet. |
| `test_object_cache` | read | Live probe of the Redis or Memcached server. |
| `cloudflare_verify` | read | Check the Cloudflare connection on a site. |
| `get_speed_scan` | read | Read an xSpeed Scan report or a site's scan history. |
| `run_benchmark` | read, every site | Measure the site's own cached versus uncached response time. No Lighthouse score. |
| `purge_cache` | write, every site | Purge all, page, assets, object or REST cache. |
| `toggle_cache` | write, every site | Turn page caching on or off. |
| `update_settings` | write, every site | Change one module's settings. |
| `start_preloader` | write, every site | Start warming the cache. |
| `stop_preloader` | write, every site | Stop the cache preloader. |
| `optimize_site` | write, every site | Apply a safe, standard or aggressive optimization pass, or preview it with dry_run. |
| `toggle_object_cache` | write | Turn the Redis or Memcached object cache on or off. |
| `flush_object_cache` | write | Empty the object cache. |
| `purge_cloudflare` | write | Purge the Cloudflare edge cache for a site. |
| `set_cloudflare_dev_mode` | write | Turn Cloudflare development mode on or off (about three hours). |
| `generate_critical_css` | write | Generate critical CSS. Needs the Pro Critical CSS module on the site. |
| `run_speed_test` | write (spends speed-test allowance) | Run a PageSpeed Insights test from the Hub, mobile or desktop. |
| `run_speed_scan` | write (spends speed-test allowance) | Run a full graded xSpeed Scan with a shareable report link. |

## Can an AI agent change my site without asking?

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.

## Frequently asked questions

### What does it mean to manage WordPress caching with an AI agent?

It means an AI agent such as Claude Code, ChatGPT, Cursor or Gemini CLI reads your cache status, purges, tunes settings and runs speed tests on your WordPress sites for you. With xSpeed the agent calls the xSpeed Hub MCP server, which forwards each tool call to the xSpeed Cache plugin on the site you named.

### Which AI agents work with xSpeed?

Any client that can connect to a remote MCP server over HTTP. This section has a guide for 24 of them: Claude Code, Claude, Claude Cowork, ChatGPT, Codex, Cursor, GitHub Copilot in VS Code, Windsurf, Gemini CLI, Antigravity, Zed, Kiro, OpenCode, OpenClaw, Hermes Agent, Grok Build, ChatGPT dots, Grok, Grok Bot, Muse, Manus, Kimi Code, Paperclip and NanoClaw.

### Do I need an API key?

No. Clients that support OAuth open an xSpeed Hub sign-in page and you approve access in the browser, so there is nothing to paste and the client keeps the credentials it receives. Clients that only take headers can use the connection token from the Hub's Connect AI page, sent in an Authorization header. Only the workspace owner can see or mint that token.

### Can an agent change my site without asking me?

It can if your setup allows it, so set it up deliberately. xSpeed Hub has no confirmation step of its own: a write tool runs as soon as your connection allows writes. The gates are your connection's scope and your AI client's own approval prompt. A read-only connection refuses every write tool: the connection token has a Read-only everywhere switch, an OAuth sign-in carries the scopes your client asks for, and a Viewer member only ever gets read access. The Hub also tells the agent to confirm the target site and to ask once before a write that touches every site, but that is an instruction to the agent, not a lock.

### What is the difference between xSpeed Hub, the site MCP server and the Scan MCP?

xSpeed Hub is one MCP endpoint for every site in your workspace and is the route most people want. The site MCP server lives inside the xSpeed Cache plugin on one site and adds per-site extras such as database cleanup and the run_command bridge to WP-CLI. The Scan MCP needs no account and only grades public URLs; it cannot change anything.

### Is xSpeed Hub free?

Yes. The Hub is free, has no site cap and MCP access is not plan-gated. A few tools act on Pro features of the plugin, such as generating critical CSS, and those need xSpeed Cache Pro on that site.

### Can one prompt act on all of my sites?

Yes, for seven tools: purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark accept every site in a workspace in one call. The Hub runs the sites one after another with a one-second pause and returns a result per site, so a partial failure is reported site by site.

### Can an agent run xSpeed jobs on a schedule?

The Hub has no scheduler for agent prompts; it runs its own daily checks and alerts. A client that has scheduled jobs, such as OpenClaw or Hermes Agent, can call the Hub on a timer. If you schedule anything that writes, use a connection and a client rule you are comfortable leaving unattended, or make the job report only.

### What can the agent not do through the Hub?

It cannot add, remove or rename sites, change members, roles or billing, mint or rotate tokens, or widen its own access. Those stay in the Hub dashboard. Database cleanup and the WP-CLI bridge are only on the site MCP server.

## More

- xSpeed Hub: https://xspeedcache.com/xspeed-hub/
- Connecting to xSpeed Hub: https://xspeedcache.com/docs/connecting-to-xspeed-hub/
- Site MCP tool reference (the per-site server; the Hub tools are listed above): https://xspeedcache.com/docs/mcp-tool-reference/
- xSpeed Scan MCP: https://xspeedcache.com/docs/scan-mcp/