How do I connect Claude Cowork to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Claude Cowork.
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 your Claude account
Cowork does not keep its own connector list. In Claude, go to Customize > Connectors, click Add custom connector, name it xspeedhub, paste the URL, choose Sign in now and, if asked, Register automatically. The full steps, including the Team and Enterprise route, are on the Claude page: /agent/claude/.
https://app.xspeedcache.com/xspeed/mcp
3Connect, then start a new Cowork session
Click Connect on the connector and approve access on the xSpeed Hub page. Cowork loads the connectors enabled for your account when a session starts, so open a new Cowork session after you connect. You can also switch the connector on from the + menu in the chat box.
Customize > Connectors > xspeedhub > Connect
4Set tool permissions before the first task
Open the connector under Customize > Connectors and set each tool to Always allow, Needs approval or Blocked. A sensible start is Always allow for the read tools and Needs approval for purge_cache, toggle_cache, update_settings and the other writes. Then pick a Cowork mode; Manual is the one that shows you each request.
Tool permissions: get_cache_status = Always allow Tool permissions: purge_cache = Needs approval
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off. Do not change anything.
You: The spring sale page goes live at noon. Use xSpeed Hub to check that the shop site is ready and add what you find to launch-notes.md in my launch folder.
get_cache_status(site: shop) read-only
→ page cache on, 205 cached pages, hit ratio 61% in the last 24h
get_score_history(site: shop) read-only
→ latest stored PageSpeed run 9 days ago: mobile 64, desktop 88
Claude Cowork: The cache is on with a 61% hit ratio. If the sale page changed after it was cached, visitors at noon could get the old copy. I would purge the page cache on shop and start the preloader so the first visitors get a stored copy. Go ahead?
You: Yes, purge pages only and warm it.
purge_cache(site: shop, type: page) changes site
→ page cache purged (205 entries); object cache and assets untouched
start_preloader(site: shop) changes site
→ preloader started, 205 URLs queued
Claude Cowork: Done. I added the cache status, the last stored scores and the purge to launch-notes.md. The hit ratio will read low until the preloader finishes.
Using it
Prompts to try in Claude Cowork
Paste one as it is, or change the site name.
Use xSpeed Hub to check the cache status of every site and write a one-page summary into cache-report.md in this folder.
Before the 2pm launch, use xSpeed Hub to purge the page cache on shop, start the preloader and report the hit ratio afterward.
With xSpeed Hub, compare the last three stored PageSpeed runs on the blog site and put the numbers in a small table.
Ask xSpeed Hub to preview a safe optimize_site pass on docs without applying it, and list what it would change.
Using xSpeed Hub, which of my sites has page caching turned off? Do not change anything.
What can Claude Cowork do with xSpeed?
A guide for each job, written for Claude Cowork.
Purge the WordPress cache with Claude Cowork
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 Cowork
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 Cowork
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 Cowork
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 Cowork
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 Cowork
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 Cowork
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Claude Cowork
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Claude Cowork
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 Cowork
Run one action across all of your sites, or a chosen few, and read the result site by site.
Trust and safety
Does Claude Cowork ask before it changes my site?
Cowork has three modes. Manually approve (Manual) pauses and asks you to Allow or Deny each action. Automatically approve (Auto) keeps working and blocks what Claude judges to be unsafe. Skip all approvals (Skip) asks nothing and checks nothing. Each connector tool also has a permission, set under Customize > Connectors. In Manual mode, Always allow runs, Needs approval asks and Blocked is denied; in Skip mode only Blocked stops a call. xSpeed Hub has no confirmation step of its own, so under Skip, or for any tool set to Always allow, a write runs as soon as your connection allows writes. Auto relies on Claude's own judgement, which is not a lock.
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
- Add the connector in Claude first, and open a new Cowork session afterward, because Cowork syncs connectors at session start.
- Skip all approvals asks nothing and checks nothing. Do not use it with the Hub's write tools unless you have also set them to Blocked or signed in as a Viewer member of the workspace, which is always read-only.
- In Auto mode Claude decides for write tools set to Always allow and for tools set to Needs approval. That is a judgement by the model, so keep Manual for anything you want to see first.
- If a Dispatch task asks for approval and you do not answer within ten minutes, the request is denied and the task continues without that action.
Reference
What is Claude Cowork?
Claude Cowork is Anthropic's agentic workspace in the Claude desktop app. It uses the same agent architecture as Claude Code without a terminal: you describe an outcome, and Claude works through the steps on its own, reading and writing local files and calling the connectors you have enabled.
Cowork does not keep a separate list of connectors. It loads the ones enabled for your claude.ai account, synced at session start, so xSpeed Hub appears in Cowork after you add it as a custom connector in Claude. Anthropic's servers make the connection to the Hub, not your computer, and the Hub is reachable on the public internet.
At a glance
- Made by
- Anthropic
- Type
- Desktop agent
- Connects with
- A custom connector added to your Claude account
- Sign-in
- OAuth sign-in
- Last checked
- October 2026
Why use Claude Cowork with xSpeed?
A cache check inside a bigger task
Cowork is built for multi-step work with files. Fold a status check, a purge and a warm-up into a launch checklist, then have it write the result into a document in the same session.
Modes and per-tool permissions
Manual, Auto and Skip set how often Cowork stops. Always allow, Needs approval and Blocked set what each Hub tool may do. Together they let you keep reads quiet and writes in front of you.
Start a task from your phone
With Claude Desktop open, Dispatch lets you start a task from the Claude mobile app and have it run on your computer. Dispatch needs a Pro or Max plan.
How does Claude Cowork 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 Cowork | Anthropic | Desktop agent | A custom connector added to your Claude account | OAuth sign-in |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token |
| 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 Cowork 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