How do I connect Claude Code to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Claude Code.
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 Claude Code
Run this once. --scope user makes the server available in every project; leave it off and it applies to the current project only, which is Claude Code's default.
claude mcp add --transport http --scope user xspeedhub https://app.xspeedcache.com/xspeed/mcp
3Sign in with /mcp
Start Claude Code, run /mcp, pick xspeedhub and finish the sign-in in your browser. You approve access on an xSpeed Hub page; there is no token to paste, and Claude Code keeps the credentials it receives and refreshes them.
/mcp
4Or use a connection token alternative
If you prefer a header to a browser sign-in, copy the connection token from Connect AI in the Hub (only the workspace owner sees it) and pass it with --header. A rejected header shows as a failed connection rather than falling back to sign-in.
claude mcp add --transport http --scope user xspeedhub https://app.xspeedcache.com/xspeed/mcp \ --header "Authorization: Bearer <your connection token>"
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
You: The shop site feels slow after this morning's deploy. Use xSpeed Hub to find out what is going on.
list_sites read-only
→ 6 sites; shop is shop.example.com
get_cache_status(site: shop) read-only
→ page cache on, 312 cached pages, hit ratio 38% in the last 24h
Claude Code: Caching is on but most requests miss, and nothing here shows why yet. The deploy may have changed asset URLs so the stored pages point at old files, but I have not confirmed that. A page-cache purge and a fresh warm-up rebuild the stored pages either way, and leave the object cache alone. Purge pages on shop and start the preloader?
You: Yes, go ahead.
purge_cache(site: shop, type: page) changes site
→ page cache purged (312 entries); assets and object cache untouched
start_preloader(site: shop) changes site
→ preloader started, 340 URLs queued
Claude Code: Done. The preloader is warming 340 URLs; ask me in a few minutes and I will check the hit ratio again. If it stays low, I will run get_health next.
Using it
Prompts to try in Claude Code
Paste one as it is, or change the site name.
Use xSpeed Hub to show the cache hit ratio for every site and flag anything under 70%.
With xSpeed Hub, purge the blog site, 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 last one in the score history.
Ask xSpeed Hub to preview what optimize_site would change on the docs site with a safe pass. Do not apply it.
Using xSpeed Hub, check whether Redis is reachable on shop before you turn on the object cache.
What can Claude Code do with xSpeed?
A guide for each job, written for Claude Code.
Purge the WordPress cache with Claude Code
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 Claude Code
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 Claude Code
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 Claude Code
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 Claude Code
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 Claude Code
See which modules a site has, read their current settings, change them, and turn page caching on or off.
Warm the WordPress cache with Claude Code
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Claude Code
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Claude Code
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 Claude Code
Run one action across all of your sites, or a chosen few, and read the result site by site.
Trust and safety
Does Claude Code ask before it changes my site?
Claude Code asks before it runs an MCP tool unless a permission rule already allows it, or you work in auto mode, where a classifier reviews actions instead of you, or in bypassPermissions mode, which skips prompts. A rule such as mcp__xspeedhub__get_cache_status allows one tool, and mcp__xspeedhub__get_* allows every read whose name starts with get_. Keep purge_cache, update_settings, toggle_cache and the other write tools on the prompt, because the Hub itself runs a write as soon as your connection allows it.
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
- Without --scope user the server is added to the current project only, so it will look missing when you start Claude Code in another folder.
- If you add the same server name in two scopes with different URLs, Claude Code warns about the conflict and stores a separate sign-in per URL. Keep one entry.
- In claude -p and other non-interactive runs there is no /mcp panel, so sign in first with /mcp in an interactive session or with claude mcp login xspeedhub.
Reference
What is Claude Code?
Claude Code is Anthropic's agentic coding tool. It runs in your terminal and in IDE extensions, reads and edits code, runs commands, and calls tools on MCP servers you add to it.
MCP, the Model Context Protocol, is how Claude Code reaches services outside your machine. Adding xSpeed Hub as a remote HTTP server gives it the Hub's caching tools: status, purge, settings, preloader, object cache, Cloudflare and speed tests, for every site in your workspace.
At a glance
- Made by
- Anthropic
- Type
- Terminal
- Connects with
- claude mcp add, then /mcp to sign in
- Sign-in
- OAuth sign-in or connection token
- Last checked
- October 2026
Why use Claude Code with xSpeed?
Purge where you deploy
You already ship from the terminal. Ask Claude Code to purge the site you just deployed and warm it again, in the same session that pushed the code.
Permission rules per tool
Every xSpeed tool has its own name in Claude Code, so you can allow the reads once and keep each write behind a prompt.
One server for the whole fleet
The Hub fronts every site you connected. "Purge all my sites" is one tool call that returns a result per site.
How does Claude Code 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 |
|---|---|---|---|---|
| Claude Code | Anthropic | Terminal | claude mcp add, then /mcp to sign in | OAuth sign-in or connection token |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token |
| Claude Cowork | Anthropic | Desktop agent | A custom connector added to your Claude account | OAuth sign-in |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in |
| Cursor | Anysphere | Editor | mcp.json with a url, then OAuth | OAuth sign-in or connection token |
Which way should I connect?
Claude Code 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