# Manus + xSpeed: Manage WordPress Caching

> Manus is a general AI agent that takes a task from request to finished result, and with xSpeed Hub added as a custom MCP server it can read cache status, purge, change settings and run speed tests on every WordPress site in your workspace as part of a longer job. You add the server once in Settings and name xSpeed Hub in the task.

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

- One custom MCP server in Settings, every site you connected to the Hub
- A connection token you can switch to Read-only everywhere for unattended work
- Scheduled tasks for a recurring, report-only cache check

## How do I connect Manus 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, 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
```

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

### 4. Let 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.
```

**Authentication:** Connection token. Manus documents an API key or Bearer token for a custom MCP server and describes no browser sign-in for one. Use the connection token from the Hub's Connect AI page, which only the workspace owner can see, as the Bearer token.

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

## Does Manus ask before it changes my site?

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.

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 audit every site and prepare one list of fixes, ordered by impact. Ask me before changing anything.
  → list_sites [read-only]: 4 sites: shop, blog, docs, landing
  → get_cache_status(site: shop) [read-only]: page cache on, hit ratio 79% in the last 24h
  → get_object_cache_status(site: shop) [read-only]: object cache off; Redis detected on the server
  → test_object_cache(site: shop) [read-only]: Redis reachable, round trip 0.4 ms
Agent: The biggest fix is on shop: Redis is installed and reachable, but the object cache is off, so every page rebuilds its database queries. Turning it on changes how shop runs. Turn on the object cache on shop?
You: Yes, turn it on.
  → toggle_object_cache(site: shop, enabled: true) [changes site]: object cache enabled on shop (Redis)
Agent: Done. shop now keeps query results in Redis. I will read blog, docs and landing next and add their fixes to the list.
```

## What is Manus?

Manus is a general AI agent. You describe a task in plain words and it works through the steps, such as research, writing and acting in other apps, until it has a result for you.

Manus reaches other apps through connectors. Prebuilt ones sign in with OAuth and you use one by mentioning the app in your prompt. For anything outside its directory, Manus supports custom MCP servers, added under Settings, Integrations, Custom MCP Servers with a name, an HTTPS server URL and a credential such as a Bearer token. MCP, the Model Context Protocol, is how that server describes its tools, and adding xSpeed Hub this way gives Manus the Hub's caching tools for every site in your workspace.

## Why use Manus with xSpeed?

- **Hand off the whole audit**: Ask for an audit of every site and Manus works through the Hub's reads, from cache status to the object cache, then brings back one list of fixes to approve.
- **Name the server, skip the tool names**: You do not need to know the Hub's tool names. Mention xSpeed Hub in the task and Manus picks the tools it needs.
- **A weekly report with no write access**: A scheduled task on a read-only token can read every site and write you a summary, and the Hub refuses any write it attempts.

## Good to know

- xSpeed Hub is not in the Manus connector directory. You add it as a custom MCP server and mention it in your prompt so Manus uses it.
- The connection token reaches every site in the workspace. Anyone holding it can use the Hub's tools, so keep it out of chats and rotate it on the Connect AI page if it leaks.
- Scheduled tasks run unattended and can skip confirmations. Keep that setting off for any task that might write, and prefer a token with Read-only everywhere on.
- Rotating or disconnecting the token in the Hub cuts off Manus and any other client that sends the same token.

## Prompts to try

- Use xSpeed Hub to show the cache hit ratio for every site and flag anything under 70%.
- With xSpeed Hub, find every site whose preloader has not run in a week and warm them, asking me once first.
- Use xSpeed Hub to run a mobile PageSpeed test on shop and compare it with the stored score history.
- With xSpeed Hub, check whether Redis is reachable on blog and tell me what turning on the object cache would change.
- Use xSpeed Hub to list the modules on landing and tell me which ones are off, without changing any.

## Schedule a report-only cache check

Manus runs scheduled tasks on a timetable, unattended, and they can use your connected servers. The Hub has no scheduler for agent prompts, so the timer is Manus's. Nobody is there to approve a change during a run, so word the task as report only, use the Test run option with that same prompt, leave skip confirmations off, and send it through a connection token with Read-only everywhere on.

```
Every Monday at 8:00, use xSpeed Hub to read the cache status and preloader status of every site. Write me a short report: any site with page caching off, a hit ratio under 70%, or a preloader that has not run in a week. Report only: do not purge, toggle, change settings or run speed tests.
```

## What can Manus do with xSpeed?

- [Purge the WordPress cache with Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/object-cache/): Connect a site to Redis or Memcached so database results survive between requests.
- [Manage Cloudflare caching with Manus](https://xspeedcache.com/agent/manus/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 Manus](https://xspeedcache.com/agent/manus/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 Manus to xSpeed Hub?

Copy the connection token from Connect AI in xSpeed Hub. In Manus, open Settings, then Integrations, then Custom MCP Servers, click Add Server, enter a name, the URL https://app.xspeedcache.com/xspeed/mcp and the token as the Bearer token. Manus checks the server and reads its tools, and you can then name xSpeed Hub in a task.

### Do I need an API key?

You need the Hub's connection token, which only the workspace owner can see on the Connect AI page. Manus documents an API key or Bearer token for custom MCP servers and describes no browser sign-in for them, so the token is the route here.

### Will Manus change my site without asking?

It can. Manus describes no per-tool approval setting for a custom server, and xSpeed Hub has no confirmation step of its own, so a write runs once Manus calls it. Ask Manus in the task to check with you before any change, and for a firm stop turn on Read-only everywhere on the token, which makes the Hub refuse every write tool.

### Can Manus check my sites on a schedule?

Yes. Manus scheduled tasks run on a timetable and can use your connected servers. Word the task as report only, leave skip confirmations off, and use a token with Read-only everywhere on so nothing can change while nobody is watching.

### Is xSpeed Hub listed as a Manus connector?

No. You add it yourself as a custom MCP server. Once it is added, mention xSpeed Hub in your prompt so Manus uses it.

### Can Manus work on all of my sites at once?

Yes. One server reaches every site in the workspace, and seven Hub tools accept every site in one call, such as purge_cache and start_preloader. The Hub returns a result per site, so Manus can report which ones failed.

### How do I disconnect Manus?

Remove the server under Settings, Integrations, Custom MCP Servers in Manus. 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/) · [Muse](https://xspeedcache.com/agent/muse/) · [Kimi Code](https://xspeedcache.com/agent/kimi/) · [Paperclip](https://xspeedcache.com/agent/paperclip/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/)

## Sources

- Manus Docs: Custom MCP servers: https://manus.im/docs/integrations/custom-mcp
- Manus Docs: MCP connectors: https://manus.im/docs/integrations/mcp-connectors
- Manus Docs: Automations: https://manus.im/docs/automations
- Manus: Scheduled Tasks 2.0: https://manus.im/blog/manus-schedules