# Muse + xSpeed: Manage WordPress Caching from Chat

> Muse is Meta's personal AI agent, which takes actions for you and runs in the Muse app, on muse.ai and inside WhatsApp, and with xSpeed Hub added as a custom connector it can read cache status, purge, change settings and run speed tests on your WordPress sites from a chat thread. You ask Muse to create the connector once and answer from wherever you message it.

Page: https://xspeedcache.com/agent/muse/
Last updated: October 2026

- No settings form: you ask Muse to create the connector in a chat
- The connection token can be set to Read-only everywhere, so Muse can look but not change
- Check a site from the Muse app, muse.ai or WhatsApp

## How do I connect Muse to xSpeed?

### 1. Put 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.

### 2. Copy 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)
```

### 3. Ask 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.
```

**Authentication:** Connection token. Meta says creating a custom connector can involve retrieving API information from the service, which Muse keeps in its Secure Credentials Store. For xSpeed Hub that credential is the connection token from the Hub's Connect AI page, which only the workspace owner can see. If Muse offers a browser sign-in instead, the Hub supports that too.

**Check it worked:** ask "Use xSpeed Hub to list my sites and tell me which ones have page caching turned off. Do not change anything."

## 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 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.

## Example session

```
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
Agent: 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
Agent: Page caching is on for blog. It starts empty, so the first visits fill it. I can start the preloader to warm it now.
```

## 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.

## 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.

## 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.

## Prompts to try

- 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?

- [Purge the WordPress cache with Muse](https://xspeedcache.com/agent/muse/purge-cache/): 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](https://xspeedcache.com/agent/muse/troubleshoot-cache/): 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](https://xspeedcache.com/agent/muse/speed-scan/): 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](https://xspeedcache.com/agent/muse/pagespeed-tests/): 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](https://xspeedcache.com/agent/muse/optimize-site/): 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](https://xspeedcache.com/agent/muse/cache-settings/): 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](https://xspeedcache.com/agent/muse/preload-cache/): Fill the page cache before visitors arrive, for example right after a purge or a deploy.
- [Set up the Redis object cache with Muse](https://xspeedcache.com/agent/muse/object-cache/): Connect a site to Redis or Memcached so database results survive between requests.
- [Manage Cloudflare caching with Muse](https://xspeedcache.com/agent/muse/cloudflare/): 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](https://xspeedcache.com/agent/muse/fleet/): Run one action across all of your sites, or a chosen few, and read the result site by site.

## Which way should I connect?

| Surface | Endpoint | Reaches | Auth | Tools |
| --- | --- | --- | --- | --- |
| [xSpeed Hub MCP](https://xspeedcache.com/docs/hub-mcp/) | `https://app.xspeedcache.com/xspeed/mcp` | Every site in your workspace, one connection | OAuth sign-in in the browser, or a connection token in an Authorization header | 29 tools (16 read, 13 write), seven of them can act on every site at once |
| [xSpeed Cache Site MCP](https://xspeedcache.com/docs/mcp-server/) | `https://your-site.com/xspeed/mcp` | One WordPress site | OAuth sign-in by a site admin, or the site's own token in an Authorization header | The full per-site tool set plus run_command for the WP-CLI surface |
| [xSpeed Scan MCP](https://xspeedcache.com/docs/scan-mcp/) | `https://xspeedcache.com/scan/mcp` | Any public URL, read-only | None. No account. | 5 tools: run_speed_scan, get_speed_scan and three product-info tools |
| [WP-CLI](https://xspeedcache.com/docs/wp-cli-commands/) | `wp xspeed …` | The site whose server the agent has a shell on | Your server login | Every xSpeed command: cache, purge, preloader, objcache, cf, score, settings and more |

## Frequently asked questions

### How do I connect Muse to xSpeed Hub?

Copy the connection token from Connect AI in xSpeed Hub. Then ask Muse to create a custom connector for the MCP server at https://app.xspeedcache.com/xspeed/mcp and follow the steps it gives you, giving it the token as a Bearer token when it asks for the credential.

### Do I need an API key?

You use the Hub's connection token, which only the workspace owner can see on the Connect AI page. Meta says Muse keeps the credentials for a custom connector in its Secure Credentials Store. If Muse offers a browser sign-in instead, the Hub supports that as well.

### Is xSpeed Hub a listed Muse connector?

No. You add it as a custom connector by asking Muse. Meta says it does not review custom connectors, so create it only from a request you sent yourself.

### Will Muse change my site without asking?

Meta says Muse will not take many important actions without your approval by default, and you can change when it asks in Settings. xSpeed Hub has no confirmation step of its own, so the firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Turn it off only when you want Muse to act.

### Where can I use Muse with xSpeed Hub?

Wherever you chat with Muse: the Muse app, muse.ai or WhatsApp. Muse is rolling out in the US first, so availability depends on whether you have access yet.

### Can I use it with one site and no Hub?

The Hub is the route this page covers, because one connector then reaches every site. The xSpeed Cache plugin also has its own MCP server on each site, at your-site.com/xspeed/mcp, if you only run one.

### How do I disconnect Muse?

Disconnect the connector in Muse under Settings, Connectors. To cut access on the Hub side too, rotate or disconnect the connection token on the Connect AI page, which also cuts off any other client that sends it.

## Also works with

[Claude Code](https://xspeedcache.com/agent/claude-code/) · [Claude](https://xspeedcache.com/agent/claude/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/) · [Codex](https://xspeedcache.com/agent/codex/) · [Cursor](https://xspeedcache.com/agent/cursor/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/) · [Windsurf](https://xspeedcache.com/agent/windsurf/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/) · [Antigravity](https://xspeedcache.com/agent/antigravity/) · [Zed](https://xspeedcache.com/agent/zed/) · [Kiro](https://xspeedcache.com/agent/kiro/) · [OpenCode](https://xspeedcache.com/agent/opencode/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/) · [Grok Build](https://xspeedcache.com/agent/grok-build/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/) · [Grok](https://xspeedcache.com/agent/grok/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/) · [Manus](https://xspeedcache.com/agent/manus/) · [Kimi Code](https://xspeedcache.com/agent/kimi/) · [Paperclip](https://xspeedcache.com/agent/paperclip/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/)

## Sources

- Meta Help Center: How Muse works with Connectors: https://www.meta.com/help/artificial-intelligence/1687253048996149/
- Meta: Introducing Muse: https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/