How do I connect Claude to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Claude.
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 as a custom connector
Go to Customize > Connectors and click Add custom connector. Name it xspeedhub and paste the URL. Under Authentication choose Sign in now, and if Claude asks how it identifies itself, choose Register automatically, which uses dynamic client registration. Click Add. On a Team or Enterprise plan an Owner does this under Organization settings > Connectors, with Add, then Custom, then Web.
https://app.xspeedcache.com/xspeed/mcp
3Connect and turn it on in a chat
Click Connect on the xspeedhub connector and approve access on the xSpeed Hub page that opens. Then, in a conversation, click + in the message box, choose Connectors and switch xspeedhub on. Claude can use the connector only in conversations where that toggle is on.
+ > Connectors > xspeedhub (on)
4Or send the connection token in a header alternative
Only if your organization has the Request headers beta. Choose No sign-in as the Authentication setting, open Request headers, pick the authorization header and enter Bearer, a space, then the connection token from Connect AI in the Hub. Claude sends the value exactly as typed. Only the workspace owner sees that token, and you cannot edit authentication settings later, so remove and re-add the connector to change them.
Header: authorization Value: Bearer <your connection token>
Use the xSpeed Hub connector to list my sites and tell me which ones have page caching turned off.
You: My docs site feels slow for visitors who are not logged in. Can you check its cache with xSpeed Hub?
list_sites read-only
→ 4 sites; docs is docs.example.com
get_cache_status(site: docs) read-only
→ page cache on, 188 cached pages, hit ratio 52% in the last 24h
get_preloader_status(site: docs) read-only
→ preloader idle, last run 6 days ago, 41 URLs not warmed
Claude: Caching is on, but the preloader has not run for six days and 41 pages are still cold, so some visitors get an uncached response. Start the preloader on docs?
You: Yes, start it.
start_preloader(site: docs) changes site
→ preloader started, 41 URLs queued
Claude: Started. Ask me again in a few minutes and I will compare the hit ratio.
Using it
Prompts to try in Claude
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.
Using xSpeed Hub, is Redis reachable on shop? Test it before you suggest turning on the object cache.
Using xSpeed Hub, which of my sites would benefit from a Pro feature? Summarize the audit in three lines.
What can Claude do with xSpeed?
A guide for each job, written for Claude.
Purge the WordPress cache with Claude
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
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
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
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
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
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
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Claude
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Claude
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
Run one action across all of your sites, or a chosen few, and read the result site by site.
Trust and safety
Does Claude ask before it changes my site?
Claude can ask for your approval before it uses a connector tool. Allow once runs that call, and Always allow skips the prompt for that tool from then on. Under Customize > Connectors you can set each tool, or a group of tools, to Always allow, Needs approval or Blocked. xSpeed Hub has no confirmation step of its own, so a write tool you set to Always allow runs as soon as your connection allows writes. Keep purge_cache, update_settings, toggle_cache and the other write tools on Needs approval, block the ones you never want. For read-only access, sign in as a Viewer member of the workspace, or use the connection token with Read-only everywhere on, which needs the Request headers beta. The switch does not apply to a normal OAuth sign-in.
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
- On the Free plan you can add one custom connector. On Team and Enterprise plans an Owner adds it for the organization, and each member then clicks Connect with their own account.
- You cannot change a connector's authentication settings after you add it. Remove it and add it again, and members then reconnect.
- The connector is off in a conversation until you switch it on from + > Connectors.
- Anthropic notes that Research can call connector tools without further approval. Block the Hub's write tools before you use Research with this connector.
Reference
What is Claude?
Claude is Anthropic's AI assistant. You use it at claude.ai, in the Claude desktop app and in the mobile apps, and it can call tools on remote MCP servers that you add as custom connectors.
MCP, the Model Context Protocol, is the open standard Anthropic created for connecting AI apps to tools and data. Claude reaches a custom connector from Anthropic's cloud rather than from your device, so the server has to be reachable on the public internet. xSpeed Hub is, which is why one URL is all it takes to give Claude the Hub's caching tools for every site in your workspace.
At a glance
- Made by
- Anthropic
- Type
- Chat app
- Connects with
- Customize, Connectors, Add custom connector
- Sign-in
- OAuth sign-in or connection token
- Last checked
- October 2026
Why use Claude with xSpeed?
Ask from wherever you chat
A connector you add to your account is available in conversations on the web, the desktop app and mobile. Check a site's cache from your phone without opening wp-admin.
Permissions per tool
Claude lists the connector's tools under Customize > Connectors. Let the reads run, keep each write on Needs approval, and block anything you never want called.
One connector 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, and Claude reports which sites failed, if any.
How does Claude 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 | 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 |
| Claude Code | Anthropic | Terminal | claude mcp add, then /mcp to sign in | OAuth sign-in or connection token |
| 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 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