How Muse handles this
You are on your phone, in WhatsApp or the Muse app, looking at your own shop the way customers see it, and product pages take a long time to settle. You message Muse and ask why. With xSpeed Hub added as a custom connector, Muse calls get_settings for the lazy loading module on shop, and list_modules if it needs to see what else is on, so it can tell you whether images below the fold load straight away or wait until a visitor scrolls to them.
What comes back is a short answer that fits a phone screen: lazy loading for images is off, so every product photo downloads before the page is usable, and turning it on is a single setting. The Hub tells the agent to briefly confirm intent before update_settings, so Muse asks in the thread. If your connection token still has Read-only everywhere on, which is the safe way to start with Muse, the Hub refuses the write and says the connection is read-only. That is the switch doing its job. Turn it off on the Connect AI page when you want Muse to apply changes, or make the change yourself in the xSpeed dashboard. With writes allowed, a wrong key or value refuses the whole call and nothing is stored, and credential fields are refused over the Hub.
What differs in Muse is how you set it up and where the gates are. You ask Muse to create the custom connector, and it keeps the connection token in its Secure Credentials Store. Meta says Muse will not take many important actions without your approval by default, that you change when it asks in Settings, and that a separate Sentinel agent decides what leaves its secure machine. Those are the checks Muse runs. xSpeed Hub has no confirmation step of its own, so with writes allowed a settings change runs as soon as Muse calls it.
Set up Muse once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Muse 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.
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.
Full Muse 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. 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.
What do I ask?
Three prompts written for Muse. More for this job are below.
Use xSpeed Hub to tell me why product pages on shop are slow on my phone. Read the settings only.
With xSpeed Hub, turn on lazy loading for images on shop, and tell me the setting before and after.
Ask xSpeed Hub which modules are on for blog, in one short line each.
What happens, step by step
Every xSpeed feature is a module with its own settings. Through xSpeed Hub an agent can list the modules a site has, read one module's settings, change them with a checked update, and turn page caching on or off. The site validates every write against the module's own schema, so a wrong key or value is refused with a reason instead of being quietly ignored.
01
List the modules
list_modules returns every Free and Pro module available on one site, with its settings schema and status. It tells the agent which module slugs exist, such as minify or gzip, and what each setting accepts.
02
Read the current settings
get_settings takes a module slug and returns its settings. Credential fields come back masked, so an agent cannot read a stored API token or password back in plain text.
03
Change them
update_settings takes the module and a values object of setting keys. The site checks the whole object first. If any key is unknown, any value is outside the schema, or a field is pinned by a constant in wp-config.php, it refuses the write, writes nothing and says which keys and why, sometimes with a "did you mean" hint.
04
Turn page caching on or off
Page caching has its own tool, toggle_cache, because it installs or removes the cache drop-in and the WP_CACHE constant. Asking update_settings to set cache_enabled does not work and is refused. If another caching plugin owns the drop-in, the site declines to enable xSpeed and returns blocked: true with the reason.
05
Check the effect
The result of a settings write is the stored settings. A module can add a warning when a setting is saved but has no effect on this server, for example Brotli on a server without the module for it, and the agent should pass that on. run_benchmark then times cached against uncached to see whether the change helped.
06
Apply to many sites only after reading one
update_settings and toggle_cache accept site: "all" or a list of handles. Each site validates against its own schema and answers in its own row, so a module missing on one site fails that row and the others still apply. Read one site first, then apply.
Reference
| Discover | list_modules (read): Free and Pro modules, settings schema, status, per site |
|---|---|
| Read settings | get_settings (read): argument module; credential fields masked |
| Change settings | update_settings (write): arguments module and values; validated by the site |
| Bad input | The whole write is refused and nothing is written; the error names the keys and reasons |
| Page cache on or off | toggle_cache (write): argument enabled; cache_enabled in update_settings is refused |
| Blocked by another plugin | toggle_cache returns blocked: true with blocked_reason when another plugin owns the cache drop-in |
| Every site at once | update_settings and toggle_cache accept site: "all" or a list of handles, one result per site |
| Pro modules | A Pro module on a site without an active licence cannot be read or written; the site refuses |
| Credential fields | Refused by default over MCP; set them in the xSpeed dashboard, not through the agent |
| Read-only connection | The connection token with Read-only everywhere on, or a Viewer member's sign-in: update_settings and toggle_cache are refused; list_modules and get_settings still work. An OAuth sign-in gets the scopes the client asks for, read and write by default, clamped to the member's role |
| Confirmation | None on the Hub; the Hub tells the agent to briefly confirm intent for these two, and your client's prompt is the gate |
Rules worth keeping
- Read before you write. Ask for list_modules and get_settings first, so the agent changes real keys with valid values instead of guessing.
- update_settings and toggle_cache change how a live site behaves. They run as soon as your connection allows writes. The Hub tells the agent to briefly confirm intent first, which is guidance to the agent, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates. The switch does not limit an OAuth sign-in.
- For site: "all", the Hub tells the agent to confirm once with "this will touch all N sites", then make one call. The result is per site, and some sites failing is a partial result to report, not a blanket success or failure.
- Do not ask an agent to set credentials such as a Cloudflare token or Redis password. The site refuses those writes by default, and they belong in the xSpeed dashboard.
- If a settings result says a value is saved but inactive on this server, relay that. Do not tell the user the feature is enabled.
Good to know with Muse
Only the workspace owner can see the connection token, and one token serves every client that sends it, so turning off Read-only everywhere for Muse also lets any other client using that token write. Turn it back on when you are done with settings work. Meta does not review custom connectors, so create this one only from a request you sent yourself, and Muse is rolling out in the US first. Disconnecting later stops new access, but what Muse already read may stay in its memories.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to list the modules on shop and tell me which ones are off.
Ask xSpeed Hub for the current minify settings on blog.
With xSpeed Hub, turn on HTML minification on blog, then benchmark the cache and tell me if it helped.
Use xSpeed Hub to turn page caching off on staging while I debug, and tell me when it is off.
Using xSpeed Hub, read the gzip settings on shop first, then enable the same options on every site.
Use xSpeed Hub to set the page cache lifespan on docs to 30 days, and if the site refuses it, tell me why.
Frequently asked questions
Keep going
Tune cache settings with other agents
More with Muse
Documentation
- How to enable Page Cache
- How to minify CSS and JavaScript
- How to add cache rules and bypasses
- Site MCP tool reference
- How to write prompts for xSpeed Hub
- Muse + xSpeed
- Every AI agent that works with xSpeed
From the blog