How do I connect Muse to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Muse.
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.
2Copy the connection token from xSpeed Hub
Sign in at app.xspeedcache.com as the workspace owner and open Connect AI. Copy the connection token. For a first try, turn on Read-only everywhere: the Hub then refuses every write tool on that token, so Muse can read but not purge or change settings.
xSpeed Hub > Connect AI > connection token (Read-only everywhere: on)
3Ask Muse to create a custom connector
Send this message to Muse in the app, on muse.ai or in WhatsApp, and follow the steps Muse gives you. When it asks for the credential, give it the token as a Bearer token. Meta does not review custom connectors, so only finish this for the request you started yourself.
Create a custom connector called xSpeed Hub for the MCP server at https://app.xspeedcache.com/xspeed/mcp It authenticates with a Bearer token in the Authorization header. Once it is connected, use xSpeed Hub to list my sites.
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off. Do not change anything.
You: Use xSpeed Hub to tell me which of my sites is the slowest right now.
list_sites read-only
→ 3 sites: shop, blog, docs
run_benchmark(site: ["shop", "blog", "docs"]) read-only
→ shop cached 88 ms, blog cached 410 ms, docs cached 95 ms
get_cache_status(site: blog) read-only
→ page cache off
Muse: blog is the slowest: its cached response is 410 ms because page caching is off there, so every visit builds the page. Turning page caching on changes blog's settings. Turn it on?
You: Yes, turn it on.
toggle_cache(site: blog, enabled: true) changes site
→ page cache turned on for blog
Muse: Page caching is on for blog. It starts empty, so the first visits fill it. I can start the preloader to warm it now.
Using it
Prompts to try in Muse
Paste one as it is, or change the site name.
Use xSpeed Hub to show which of my sites have page caching turned off.
With xSpeed Hub, compare cached and uncached response time on shop and tell me what the gap means.
Use xSpeed Hub to read the PageSpeed score history for blog. Do not run a new test.
With xSpeed Hub, purge the page cache on docs, then tell me what it cleared.
Use xSpeed Hub to check whether the cache preloader on shop has finished warming.
What can Muse do with xSpeed?
A guide for each job, written for Muse.
Purge the WordPress cache with Muse
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 Muse
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 Muse
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 Muse
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 Muse
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 Muse
See which modules a site has, read their current settings, change them, and turn page caching on or off.
Warm the WordPress cache with Muse
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Muse
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Muse
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 Muse
Run one action across all of your sites, or a chosen few, and read the result site by site.
Trust and safety
Does Muse ask before it changes my site?
Meta says Muse will not take many important actions without your approval by default, that many connectors can be set up to only retrieve data, and that you change when Muse asks for approval in its Settings. Muse's separate Sentinel agent also decides what leaves its secure machine and asks you for permission when needed. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Muse calls it and your connection allows writes. The firm stop here is the token: with Read-only everywhere on, the Hub refuses every write tool, whatever Muse decides. Turn it off only when you want Muse to purge or change settings, and read each question Muse asks before you answer yes.
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
- Muse is rolling out in the US first, so you may not have access yet.
- xSpeed Hub is a custom connector in Muse, not a listed one, and Meta does not review custom connectors. Create it only from a request you sent yourself.
- Only the workspace owner can see the connection token. Rotating it in the Hub cuts off Muse and every other client that sends it, so plan the rotation.
- Disconnecting under Settings, Connectors stops new access, but Meta notes that what Muse already used may stay in its memories and your conversation history.
Reference
What is Muse?
Muse is a personal AI agent from Meta. It is meant to complete tasks for you rather than only answer questions, and you talk to it like a message thread in the Muse app, on muse.ai or in WhatsApp. Meta says it is rolling out in the US first, runs on a dedicated secure machine for each person, and is free for most of what people need, with subscription plans for more.
Muse reaches other services through connectors, which you add by asking Muse or from Settings, Connectors. For a service that is not in its list, you ask Muse to create a custom connector and it guides you through the steps, keeping the credentials in its Secure Credentials Store. xSpeed Hub is one MCP server, a Model Context Protocol endpoint that fronts every site in your workspace, so one custom connector gives Muse its caching tools for all of them.
At a glance
- Made by
- Meta
- Type
- Chat app
- Connects with
- a custom connector that Muse creates when you ask for it
- Sign-in
- Connection token
- Last checked
- October 2026
Why use Muse with xSpeed?
Ask from your phone
Muse lives in its mobile app and in WhatsApp as well as on the web, so you can check whether a site is cached, or why it is slow, away from your desk.
A read-only switch you control
The connection token's Read-only everywhere switch makes the Hub refuse every write. Start there, and turn it off only when you want Muse to act.
Plain questions, real numbers
Ask which site is slowest and Muse can run the Hub's benchmark across your sites and read the cache status, instead of guessing.
How does Muse 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 |
|---|---|---|---|---|
| Muse | Meta | Chat app | a custom connector that Muse creates when you ask for it | Connection token |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in |
| Claude Code | Anthropic | Terminal | claude mcp add, then /mcp to sign in | OAuth sign-in or connection token |
| Cursor | Anysphere | Editor | mcp.json with a url, then OAuth | OAuth sign-in or connection token |
Which way should I connect?
Muse 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