How Claude Cowork handles this
Cowork suits the job where you would otherwise open a dozen tabs. Maybe you are comparing your client's site with three competitors before a pitch, or checking five client sites on a Monday. You give it the list and say what the brief should contain. It calls run_speed_scan once per site, reads each report, and writes one summary: a grade for desktop and for mobile, the top failing checks, and the report link for each.
Cowork works with the connectors on your Claude account, so the xSpeed connector has to be added in Claude first. For sites that are not yours, use the no-account Scan MCP, which grades any public URL and is read-only. For your own sites inside xSpeed Hub, the Hub connector scans by site handle and can read the scan history with get_speed_scan, which spends nothing. A good brief for a client site uses both: the history for the trend, one fresh scan for today.
Keep the first request small. Ask for two sites, check that the layout of the brief is what you wanted, then send the full list. If you want the same brief every week, save the wording that worked and reuse it, and tell Cowork which grade to lead with, so the numbers line up from one week to the next.
Set up Claude Cowork once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Claude Cowork guide.
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
5Add the xSpeed Scan MCP for sites you do not run
Prompts that scan a public URL use the xSpeed Scan MCP, a separate server from the Hub. Add it to Claude Cowork the same way as the Hub above, as a second server (xspeedscan, for example) with the URL https://xspeedcache.com/scan/mcp, and leave out any sign-in setting, such as an OAuth or auth option or an Authorization header, because the Scan MCP needs no account, token or sign-in. On a plan that allows one custom connector, add whichever server the prompts you use need.
https://xspeedcache.com/scan/mcp
Full Claude Cowork setup, sign-in options and FAQ
Before you send a prompt that changes something
Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. 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.
What do I ask?
Three prompts written for Claude Cowork. More for this job are below.
Use the xSpeed Scan MCP to scan these four URLs and write one brief: desktop grade, mobile grade and the single biggest fix for each, with the report links.
With the xSpeed Scan MCP, compare [client site URL] with its two main competitors and tell me where we are weakest.
Use xSpeed Hub to read the scan history for my own sites and tell me which one has the lowest grade.
What happens, step by step
An xSpeed Scan grades a site from 0 to 100 using server probes (time to first byte, compression, cache evidence, redirects, platform detection) plus a Lighthouse run, and names the fix for every failing check. An agent can start one two ways. Through xSpeed Hub, run_speed_scan scans a site you have connected. Through the no-account Scan MCP at https://xspeedcache.com/scan/mcp, it scans any public URL and cannot change anything. Either way you get a report link to share.
01
Check what the site already scored
get_speed_scan without a scan id returns the site's scan history, newest first, plus a summary of the latest report. It starts nothing and spends nothing, so the Hub tells the agent to read it first when you ask what a site scored.
02
Start a scan
run_speed_scan runs the full scan on a site you connected to the Hub. strategy is both (the default), desktop or mobile; one device alone costs half the engine's quota. The scan takes 20 to 60 seconds. The Hub waits about 50 seconds and, if the scan is still running, hands back a scan id.
03
Poll if it is still running
Call get_speed_scan with scan_id. While the scan runs it returns the running status and a note to ask again in about 20 seconds. The report page is live from the start and refreshes itself.
04
Read the result
The summary carries the grade, the four dimension scores, what was measured and the top fixes ranked by points recoverable, each with the xSpeed feature that fixes it. The headline grade is the desktop run. The mobile run is graded alongside it, so the agent should mention both when they differ.
05
Scan a site you do not run
For any other public URL, the agent uses the Scan MCP at https://xspeedcache.com/scan/mcp. There is no account and no sign-in. It takes a url, returns the same graded report and a link at xspeedcache.com/scan/r/<id>, and is limited to 4 scans per caller per 10 minutes.
06
Fix, wait, re-scan
After a change, wait several minutes and scan again with fresh: true. Without it, the scan service reuses any report from the last 10 minutes and the agent will show you the old number.
Reference
| Hub route | run_speed_scan, then get_speed_scan with scan_id; only for sites connected to your Hub |
|---|---|
| Scan MCP route | https://xspeedcache.com/scan/mcp, no account, 5 tools, read-only, any public URL |
| Scan MCP limit | 4 scans per caller per 10 minutes |
| Why run_speed_scan is a write | It spends a shared scan allowance and stores a report; it changes nothing on the site |
| Read-only Hub connection | run_speed_scan is refused; get_speed_scan still works. Applies to the connection token with Read-only everywhere on and to a Viewer sign-in; an OAuth sign-in gets the scopes the client asks for |
| Duration | 20 to 60 seconds; the Hub waits about 50 seconds, then returns a scan id |
| Poll argument | scan_id on the Hub tool, scanId on the Scan MCP tool |
| strategy | both (default), desktop or mobile; one device costs half the quota and becomes the headline |
| fresh | true forces a new measurement; otherwise a report from the last 10 minutes is reused |
| Report link | xspeedcache.com/scan/r/<id>; add .md for a Markdown twin an agent can read |
| Report visibility | Hub scans are filed unlisted; Scan MCP scans are public in the scan directory by default |
Rules worth keeping
- Read before you spend. Ask for the scan history first; start a new scan only when you want a fresh measurement or something changed.
- A report link is not private. An unlisted report is kept out of the scan directory and search, but anyone with the URL can open it. A scan started through the Scan MCP is public by default.
- run_speed_scan changes nothing on your site, but the Hub classes it a write, so a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) refuses it and your client may prompt for it. Use get_speed_scan, or the Scan MCP for a public URL, when you want a strictly read-only route.
- Compare like with like. A scan that lost its Lighthouse run is marked partial and is not comparable with a full one, and the lab grade is not the same as real-visitor Core Web Vitals, which the report shows separately.
- A scan cannot reach private, local or password-protected sites, and a site behind a bot challenge returns a report that says its server checks were not measured.
Good to know with Claude Cowork
The no-account Scan MCP allows four scans per caller per ten minutes, so a list of eight sites will stop partway. Cowork can report which sites it finished and wait before the rest, but it cannot raise the limit. Split a long list into batches of three or four. Remember too that scan reports are public by default, so scanning a competitor creates a report anyone with the link can open. For a long Hub job, set run_speed_scan to Needs approval under Customize > Connectors and get_speed_scan to Always allow, then run in Manual mode. Skip all approvals asks nothing, so there the Hub spends the shared allowance on every scan the agent decides to start, and Auto relies on Claude's own judgement, which is not a lock.
More prompts for this job
Prompts about your own sites work in any client connected to xSpeed Hub. A prompt that scans a site you do not run, or names the scan server, needs the xSpeed Scan MCP from the setup above.
Using xSpeed Hub, what did the shop site score on its last speed scan? Do not start a new one.
Use xSpeed Hub to run a speed scan on blog and give me the three fixes that recover the most points, plus the report link.
With xSpeed Hub, scan only the mobile view of shop and tell me the grade.
I changed the theme this morning. Use xSpeed Hub to run a fresh scan on docs and compare it with the previous report.
Use the xSpeed Scan MCP to grade [competitor URL] and tell me what its biggest weaknesses are.
The speed scan on shop is still running. Ask xSpeed Hub to check it again and tell me when it finishes.
Frequently asked questions
Keep going
Scan a site's speed with other agents
More with Claude Cowork
Documentation
- xSpeed Scan: free website speed test
- xSpeed Scan MCP: speed-test any site from your AI assistant
- How to run a full site scan
- Running speed tests in xSpeed Hub
- How to write prompts for xSpeed Hub
- Claude Cowork + xSpeed
- Every AI agent that works with xSpeed
From the blog