Manus

Always-on agent

Manus + xSpeed

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.

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

Connect Manus Open xSpeed Hub

Last updated: October 2026

Manus Always-on agent

xSpeed Hub 29 tools

shop
blog
docs

Connects with Settings, Integrations, Custom MCP Servers, Add Server. Sign-in: Connection token.

How do I connect Manus to xSpeed?

Put your sites in xSpeed Hub once, then add one URL to Manus.

1Connect4 steps

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.

Text

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.

Text

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.

Text

Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.

1 / 4

2Askexample session

Check it worked

Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.

Example session · Manus

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

Manus: 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)

Manus: Done. shop now keeps query results in Redis. I will read blog, docs and landing next and add their fixes to the list.

Using it

Prompts to try in Manus

Paste one as it is, or change the site name.

Prompt

Use xSpeed Hub to show the cache hit ratio for every site and flag anything under 70%.

Prompt

With xSpeed Hub, find every site whose preloader has not run in a week and warm them, asking me once first.

Prompt

Use xSpeed Hub to run a mobile PageSpeed test on shop and compare it with the stored score history.

Prompt

With xSpeed Hub, check whether Redis is reachable on blog and tell me what turning on the object cache would change.

Prompt

Use xSpeed Hub to list the modules on landing and tell me which ones are off, without changing any.

What can Manus do with xSpeed?

A guide for each job, written for Manus.

Purge the WordPress cache with Manus

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

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

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

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

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

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

Fill the page cache before visitors arrive, for example right after a purge or a deploy.

Set up the Redis object cache with Manus

Connect a site to Redis or Memcached so database results survive between requests.

Manage Cloudflare caching with Manus

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

Run one action across all of your sites, or a chosen few, and read the result site by site.

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.

Text

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.

Trust and safety

Does Manus ask before it changes my site?

Manus

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

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

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.

Reference

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.

At a glance

Made by: Manus
Type: Always-on agent
Connects with: Settings, Integrations, Custom MCP Servers, Add Server
Sign-in: Connection token
Last checked: October 2026

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.

How does Manus 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
Manus	Manus	Always-on agent	Settings, Integrations, Custom MCP Servers, Add Server	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?

Manus 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

Read the guide →

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

Read the guide →

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

Read the guide →

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

Read the guide →

Frequently asked questions

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.

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.

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.

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.

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

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.

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

Documentation

From the blog

Sources checked (4)

Connect Manus to every site at once.

xSpeed Hub is free and has no site cap. Connect your sites, add one URL, and ask.

Open xSpeed Hub All AI agents