How Manus handles this
You have three sites and a host that recently added Redis to some of its plans, but you do not remember which sites moved. Rather than open each dashboard, you give Manus the task and name xSpeed Hub so it uses that server: find out which sites could use Redis, test each, and give me a list without changing anything. Manus calls list_sites, then get_object_cache_status for every site, and test_object_cache wherever a backend is configured but the drop-in is not installed.
What comes back is the finished list. One site already uses Redis, one has a backend configured and passes the probe, so it is ready to enable, and one has no cache server configured at all, which is a hosting task before xSpeed can do anything. None of the object-cache tools accepts every site at once, so Manus works one site per call, which suits this job. When you name the ready site, it calls toggle_object_cache with enabled set to true after asking. The site tests again when you enable and stops with Could not enable, writing nothing, if Redis does not answer.
What differs in Manus is that it is built to finish tasks with little supervision, and its custom MCP documentation describes no per-tool approval setting for a server you add. The question before the toggle comes from your request and from the Hub, which tells the agent to briefly confirm intent for the object-cache toggles. So put the stop in the task itself, change nothing until I say which site, and read the list before you answer. xSpeed Hub has no confirmation step of its own.
Set up Manus once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Manus 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, open Connect AI and copy the connection token. If Manus will only report, turn on Read-only everywhere so the Hub refuses every write tool on that token.
xSpeed Hub > Connect AI > connection token
3Add xSpeed Hub as a custom MCP server
In Manus, open Settings, then Integrations, then Custom MCP Servers, and click Add Server. Name it xSpeed Hub, enter this as the server URL, and enter the connection token as the Bearer token in the authentication field.
https://app.xspeedcache.com/xspeed/mcp
4Let Manus test it, then name it in a task
Manus checks that it can reach the server and read its list of tools. Then start a task that names xSpeed Hub, so Manus uses this server.
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
Full Manus 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. Manus's custom MCP documentation describes no per-tool approval setting for a custom server, and its scheduled tasks offer a skip confirmations option that lets Manus act without asking each time. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Manus calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, but that is an instruction. The firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Keep it on for scheduled work, and leave skip confirmations off for any task that may write.
What do I ask?
Three prompts written for Manus. More for this job are below.
Use xSpeed Hub to check which of my sites could use Redis. Test each one and give me a list. Change nothing.
With xSpeed Hub, enable the object cache on blog only, after a passing test, and read the status back.
Every Monday, ask xSpeed Hub to test Redis on every site that uses it and send me a short report. Report only.
What happens, step by step
A persistent object cache keeps database query results in Redis or Memcached instead of rebuilding them on every request. Through xSpeed Hub an agent can read the state of the cache, probe the cache server, switch the cache on or off, and flush it. The Hub tells the agent to run the probe first, because the status call alone does not prove the server is reachable.
01
Read the current state
get_object_cache_status reports whether the object-cache.php drop-in is installed, which backend is configured, Redis or Memcached, and its stats. It does not prove the server answers, so a clean status is not a green light.
02
Test the connection first
test_object_cache opens a live connection to the configured server and does a read and write probe with the settings saved on the site. A failure comes back with the server's own reason, such as a wrong password, a refused connection or a permission error. The Hub tells the agent to run this before toggle_object_cache.
03
Fix the connection if the test fails
get_settings reads the object-cache module, with secrets masked. update_settings changes it, for example the host or port. On a managed host that defines these values in wp-config.php, the fields are read-only and a write that tries to change one is refused with the name of the constant. For a host that wants the constants pasted, get_object_cache_status with detail set to snippet returns the wp-config.php block.
04
Turn it on
toggle_object_cache with enabled true makes the site test the connection again, write the connection constants into wp-config.php and install the object-cache.php drop-in. If the test fails, it stops with "Could not enable" and writes nothing. If wp-config.php is not writable, the drop-in goes in and the reply tells you to add the snippet by hand. The Hub tells the agent to briefly confirm intent first.
05
Check it took
The drop-in loads on the next request, so the agent reads get_object_cache_status again after a page load and runs test_object_cache once more. The status also warns when the cache connects but refuses writes, so a connected cache that stores nothing does not pass as healthy.
06
Flush when stale data survives
flush_object_cache empties the persistent object cache. Use it when old options, transients or query results outlive a page cache purge. It does not touch the page cache; purge_cache does that.
Reference
| Read tools | get_object_cache_status and test_object_cache, both work on a read-only connection |
|---|---|
| Write tools | toggle_object_cache (enabled true or false) and flush_object_cache |
| Backends | Redis or Memcached |
| Status detail | status (default) or snippet, the wp-config.php constants block |
| What status proves | Drop-in installed, backend configured, stats. Not that the server is reachable |
| What the test proves | A live connect and a read and write probe on the saved settings, with the server's own error on failure |
| Enable does | Tests the connection, writes connection constants to wp-config.php, installs the object-cache.php drop-in |
| Disable does | Removes xSpeed's drop-in and its wp-config.php block; a drop-in owned by another plugin is left alone |
| Connection timeout | 1 second by default, set in the object-cache module |
| Settings module | object-cache, for get_settings and update_settings |
| Every site at once | None of these tools accept site: "all"; one site per call |
| Confirmation | None on the Hub; your client's prompt is the gate |
Rules worth keeping
- Test before you toggle. The Hub tells the agent to run test_object_cache first, because a cache server that does not answer slows every request while the page cache still looks healthy.
- Keep the Redis password out of the chat. get_settings masks it, but the wp-config.php snippet is built from the saved settings and can include a saved password. Set secrets in wp-config.php or in the xSpeed panel.
- toggle_object_cache and flush_object_cache are write tools. The Hub tells the agent to briefly confirm intent for the object-cache toggles, but that is guidance, not a lock. Your client's approval prompt and a read-only grant are the gates that matter. A read-only grant means the connection token with Read-only everywhere on, or a Viewer member's sign-in; an OAuth sign-in gets the scopes the client asks for, which are read and write by default.
- If another plugin owns the object-cache.php drop-in, turn its object cache off in that plugin. xSpeed leaves a drop-in it did not install in place when you disable.
- A flush clears cached data, so the next requests rebuild it from the database and the site is briefly slower. Flush one site, then check it, before you repeat it.
Good to know with Manus
Manus sends the Hub's connection token as a Bearer token, and that token reaches every site in the workspace. While Manus is only surveying, turn on Read-only everywhere on the Connect AI page, and the Hub refuses toggle_object_cache and flush_object_cache whatever Manus decides. A scheduled task that rechecks Redis each week runs unattended and can skip confirmations, so keep that option off and the prompt report only. Do not ask for the wp-config.php snippet in a task, since it can include a saved password.
More prompts for this job
They work in any client connected to xSpeed Hub.
Using xSpeed Hub, is a persistent object cache running on shop, and which backend does it use?
Use xSpeed Hub to test whether Redis is reachable from shop. Do not change anything.
Shop is slow in wp-admin. Use xSpeed Hub to check the object cache before anything else.
With xSpeed Hub, test Redis on shop, and if it passes, turn the object cache on.
Ask xSpeed Hub for the wp-config.php object cache snippet for docs.
Use xSpeed Hub to flush the object cache on blog. Old options survive a page cache purge.
With xSpeed Hub, turn the object cache off on shop and confirm the drop-in is gone.
Frequently asked questions
Keep going
Set up Redis object cache with other agents
More with Manus
Documentation
- How to enable Redis or Memcached
- How to enable Page Cache
- Common problems and troubleshooting
- How to write prompts for xSpeed Hub
- Manus + xSpeed
- Every AI agent that works with xSpeed
From the blog