# xSpeed Cache MCP vs WP Rocket MCP in 2026: Fleet-Wide AI Control Compared

> Both plugins now ship an MCP server. The difference is architectural: WP Rocket connects one site at a time, while xSpeed Cache reaches an entire fleet — across workspaces — from a single connection.

- Published: 2026-08-26
- Author: xSpeed Cache Team
- Tags: MCP, WP Rocket, AI, Caching, Comparison, xSpeed Hub
- Canonical: https://xspeedcache.com/blog/xspeed-cache-mcp-vs-wp-rocket-mcp/

---

In February 2026 the WordPress MCP Adapter shipped as part of the AI Building Blocks initiative, and the WordPress.org plugin directory now returns **306 results** for MCP-related plugins *(according to the [WordPress.org Plugin API](https://api.wordpress.org/plugins/info/1.2/), queried 26 August 2026)*. Two of those come from performance vendors: WP Rocket introduced an MCP server in version 3.23, and xSpeed Cache ships one through xSpeed Hub.

This comparison covers what each server actually exposes, how they differ architecturally, and which fits a single site versus a portfolio. Where a claim can be checked, it links to the vendor's own documentation.

**Key takeaways**

- Both servers write. WP Rocket's MCP reads Rocket Insights data and adjusts WP Rocket settings behind an approval gate; xSpeed's writes settings, purges caches, and runs external audits.
- The architectural split is **connection model**. WP Rocket states that "each website must be connected individually." xSpeed connects sites to a Hub account, and one MCP connection reaches all of them.
- xSpeed added **cross-workspace switching** in the August 2026 Hub release, so one connection spans multiple accounts — agency workspace, personal workspace, client workspace — without re-authenticating.
- xSpeed's MCP can trigger a **real external audit** (PageSpeed Insights or GTmetrix) and compare before/after. WP Rocket's reads its own Rocket Insights scores.

---

## Quick Summary / TL;DR

**Too Long; Didn't Read?**

| If You Want To... | Use This | What It Gives You | Setup Time |
|---|---|---|---|
| Manage 1 site already on WP Rocket | WP Rocket MCP | Settings control + Rocket Insights data in chat | ~5 min, one site |
| Manage 10+ sites from one conversation | xSpeed Cache MCP | One Hub connection reaching the whole fleet | ~2 min per site, one connection |
| Run agency + client sites separately | xSpeed Cache MCP | Cross-workspace switching on one connection | One connection, many workspaces |
| Get a real PageSpeed score in chat | xSpeed Cache MCP | `run_speed_test` triggers a live external audit | Included, free tier |
| Keep a human approval gate on every change | WP Rocket MCP | Nothing applies until you approve | Default behaviour |

**Best for single-site owners already paying for WP Rocket:** WP Rocket MCP — it is included in the license you already hold, and the approval gate is a sensible default.

**Best for agencies and portfolio owners:** xSpeed Cache MCP — the fleet model means adding a site does not mean adding a connection.

**Best for teams juggling separate client accounts:** xSpeed Cache MCP — cross-workspace switching landed in the August 2026 Hub release and no competing performance MCP offers it.

---

## Why Performance MCP Servers Matter Now

The Model Context Protocol is an open standard that lets an AI assistant call tools directly instead of relying on what you paste into a chat window. For performance work, that closes a gap that has always made AI advice hard to use: a generic assistant does not know your cache hit ratio, your TTFB, or which modules you have enabled, so it produces checklists rather than fixes.

Notably, the two largest published roundups of WordPress MCP plugins — [miniOrange's](https://www.miniorange.com/blog/best-mcp-plugins-wordpress/) and [Frontman's](https://frontman.sh/blog/best-wordpress-mcp-servers-and-plugins-2026/) — cover content and CRUD servers exclusively. Neither includes a performance or caching MCP server. The category is genuinely new, which is why a direct comparison is worth writing.

For the wider field beyond these two, our [roundup of the 10 best WordPress MCP servers](/blog/best-wordpress-mcp-servers-2026/) ranks the whole category on live directory data.

## Methodology: How This Comparison Was Built

Every capability claim below comes from one of three sources, and each is marked:

1. **Vendor documentation** — WP Rocket's [MCP hub page](https://wp-rocket.me/mcp-wordpress/), [3.23 release post](https://wp-rocket.me/blog/wp-rocket-3-23/), and [knowledge base article](https://docs.wp-rocket.me/article/1922-wp-rocket-mcp).
2. **Live tool enumeration** — the xSpeed Hub MCP server's advertised tool list, read directly from an authenticated connection on 26 August 2026.
3. **First-party telemetry** — cache statistics pulled from production sites running xSpeed Cache, via the MCP server's own `get_health` tool.

Where WP Rocket's own pages disagree with each other, this article follows the more specific and more recent source (the 3.23 release post) and says so.

---

## Master Comparison Table

| Capability | xSpeed Cache MCP | WP Rocket MCP |
|---|---|---|
| Reads performance settings | ✅ | ✅ |
| Writes/adjusts settings | ✅ | ✅ (approval gate) |
| Tools exposed | 26 | 8 abilities *(per 3.23 coverage)* |
| Connection model | **One connection → whole fleet** | **Per-site connection** |
| Cross-workspace switching | ✅ (Aug 2026) | ❌ |
| Fan-out to all sites in one call | ✅ (`site: "all"`) | ❌ |
| Triggers live external audit | ✅ PageSpeed Insights / GTmetrix | ❌ (reads Rocket Insights) |
| Automated optimize → verify → revert | ✅ `optimize_site` | ❌ |
| Object cache control (Redis/Memcached) | ✅ | ❌ |
| Cloudflare purge from chat | ✅ | ❌ |
| Cache preloader control | ✅ | ❌ |
| Human approval before changes | Scope-gated at consent | Per-change approval |
| Free tier includes MCP | ✅ | ❌ (license required) |
| Entry price | $0 / $29 yr | $59 yr |

---

## The Architectural Difference That Actually Matters

Feature tables flatten the most important distinction, so it is worth stating plainly.

### WP Rocket: one connection per site

WP Rocket's 3.23 release post is explicit that a portfolio is supported — "You can connect multiple websites to the same AI tool, making it easy to manage your entire portfolio from one conversation" — but qualifies it immediately: **"each website must be connected individually. Connecting one site doesn't automatically connect your other websites."**

For a handful of sites that is a one-time cost. At 40 client sites it means 40 OAuth flows, and every new client means another one.

### xSpeed Cache: one connection per fleet

xSpeed inverts the relationship. Sites connect to a **Hub account** — a one-click link from the plugin — and the MCP connection is made once, at the Hub. From then on, the assistant reaches every site on the account. Adding the fortieth site does not touch the AI client at all.

The practical consequence is fan-out. Because the Hub knows the fleet, several tools accept `site: "all"` or an array of site handles and return per-site results from a single call:

```
purge_cache { site: "all" }
→ { summary, results: [ { site, ok, data }, … ] }
```

"Purge every site" is one call, not forty.

### Cross-workspace switching (August 2026)

The Hub release shipped in August 2026 adds a layer above the fleet: **workspaces**. A workspace owns sites, members, and billing, and one MCP connection can reach several of them.

```
list_workspaces
→ [ { workspace: "wpdeveloper",        role: "owner", sites: 8, current: true  },
    { workspace: "asif2bd-s-workspace", role: "owner", sites: 2, current: false } ]
```

Every site-scoped tool then takes an optional `workspace` argument. An agency can keep client sites in one workspace and internal properties in another, and move between them mid-conversation without re-authenticating. Reach is fixed at consent time — a workspace you did not grant shows `reachable: false`, and no tool call can widen it, which keeps the boundary meaningful.

No other WordPress performance MCP server currently offers this.

---

## xSpeed Cache MCP — Best for Portfolios and Agencies

xSpeed's MCP server is delivered through xSpeed Hub rather than by the plugin exposing an endpoint directly. That indirection is what makes the fleet model possible: the Hub is the multi-tenant layer, so the AI client never needs to know how many sites exist.

The server advertises **26 tools**, which group into five jobs.

#### Key Features

- **Measurement (7 tools):** `run_speed_test` triggers a real external audit through PageSpeed Insights or GTmetrix and returns a score with Core Web Vitals. `run_benchmark`, `get_benchmark_history`, and `get_score_history` track movement over time. `get_health` returns environment checks, 24 hourly hit/miss buckets, and a 30-day hit-ratio series.
- **Cache control (6 tools):** `purge_cache`, `toggle_cache`, `get_cache_status`, plus `purge_cloudflare`, `cloudflare_verify`, and `set_cloudflare_dev_mode` for edge caching.
- **Object cache (4 tools):** `toggle_object_cache`, `test_object_cache`, `flush_object_cache`, `get_object_cache_status` — Redis and Memcached, controllable from chat.
- **Settings and modules (4 tools):** `get_settings`, `update_settings`, `list_modules`, `get_pro_audit`.
- **Preloader and fleet (5 tools):** `start_preloader`, `stop_preloader`, `get_preloader_status`, `list_sites`, `list_workspaces`.

The one that has no counterpart elsewhere is **`optimize_site`**. Rather than handing back a list of recommendations, it measures the site, applies recommended settings **one at a time**, re-checks the page after each change, and **reverts any change that made things worse**. The closed loop — measure, change, verify, undo on regression — is the part a chat-only integration cannot replicate, because it requires both write access and an independent measurement source.

#### What the Data Looks Like

Pulled from a production site on the xSpeed fleet via `get_health` on 26 August 2026:

| Metric | embedpress.com |
|---|---|
| Cache hit ratio (24h) | **97.02%** |
| Hits / misses (24h) | 10,361 / 318 |
| Cached pages | 760 |
| Cache serving layer | nginx (PHP bypassed) |
| Hit ratio, 4 Aug → 26 Aug | 0.455 → **0.997** |

The 30-day series is the useful part: the ratio climbed from 45.5% to 99.7% as the preloader warmed pages, which is the kind of trend an assistant can read and act on directly rather than asking you to screenshot a dashboard.

#### Pros and Cons

| Pros | Cons |
|---|---|
| ✅ One connection reaches an unlimited fleet | ❌ Requires a Hub account — one extra step versus a direct plugin endpoint |
| ✅ Cross-workspace switching (Aug 2026) | ❌ Newer product with a smaller install base than WP Rocket |
| ✅ Triggers a real external PageSpeed/GTmetrix audit | ❌ External audits take up to two minutes to return |
| ✅ `optimize_site` verifies and auto-reverts regressions | ❌ Automated changes need scope granted up front |
| ✅ MCP included on the free tier | |

**Best for:** Agencies, portfolio owners, and anyone managing more than three or four WordPress sites who wants one conversation to reach all of them.

---

## WP Rocket MCP — Best for Existing Single-Site Customers

WP Rocket added MCP in version 3.23, positioning it as "The Fastest Way to Manage Performance Across Your Client Sites." Connection is by OAuth from the AI client.

#### Key Features

- **Rocket Insights access:** the assistant reads Rocket Insights scores, reports, and recommendations — WP Rocket's own performance measurements.
- **Settings read and adjust:** it can read and change WP Rocket settings.
- **Impact reporting:** it measures and reports on the effect of a change.
- **Approval gate:** per the release post, "Any change your AI suggests needs your approval before it's applied to your site. Nothing happens until you take action."
- **Reversible in-conversation:** "You can ask your AI to revert the change right from the same conversation."

WP Rocket's MCP hub page also describes MCP generally as "a read layer" that "does not hand control of your site to an AI." Read alongside the 3.23 post, the accurate reading is that changes are possible but gated: the AI proposes, and a human commits.

That is a legitimate design choice, not a deficiency. An approval gate is the conservative default, and for someone handing an assistant access to a revenue-generating site for the first time, it is the safer starting posture.

#### Pros and Cons

| Pros | Cons |
|---|---|
| ✅ Included with an existing WP Rocket license | ❌ Each site must be connected individually |
| ✅ Per-change approval gate by default | ❌ No cross-workspace or fleet-wide fan-out |
| ✅ Grounded in Rocket Insights data | ❌ No object cache, preloader, or Cloudflare control |
| ✅ Backed by a large, mature install base | ❌ No live external PageSpeed/GTmetrix trigger |
| ✅ Changes reversible in the same conversation | ❌ No free tier — license required |

**Best for:** Site owners already running WP Rocket on one or a few sites who want AI assistance without changing plugins.

---

## Feature Matrix by Job

| Job | xSpeed Cache MCP | WP Rocket MCP |
|---|---|---|
| "What's my PageSpeed score?" | ✅ Live external audit | ⚠️ Rocket Insights score |
| "Purge every site I own" | ✅ One call | ❌ Per-site |
| "Make this site faster" | ✅ Measure → apply → verify → revert | ⚠️ Proposes, you approve |
| "Switch to my client's account" | ✅ `workspace` argument | ❌ |
| "Is Redis working?" | ✅ `test_object_cache` | ❌ |
| "Warm the cache before a launch" | ✅ `start_preloader` | ❌ |
| "Purge Cloudflare's edge" | ✅ `purge_cloudflare` | ❌ |
| "Don't change anything without asking" | ⚠️ Scope-gated at consent | ✅ Per-change approval |

## Cost Breakdown

| | xSpeed Cache | WP Rocket |
|---|---|---|
| Free tier with MCP | ✅ $0 | ❌ |
| 1 site | $29 / yr — or $79 once | $59 / yr |
| 5 sites | $49 / yr — or $149 once | $119 / yr (3 sites) |
| 25 sites | $99 / yr — or $249 once | $299 / yr (50 sites) |
| Unlimited | $199 / yr — or $399 once | $599 / yr (500 sites) |

Lifetime licensing has no WP Rocket equivalent — WP Rocket is subscription-only. For an agency holding a portfolio for several years, that is the larger financial difference, ahead of the per-seat comparison.

## Common Mistakes When Connecting an AI to a Live Site

1. **Granting write scope before you have a backup.** Take a snapshot first. Write access is genuinely useful and genuinely consequential.
2. **Assuming the AI can see Core Web Vitals by default.** Most WordPress MCP servers expose content and settings, not field data. If real user metrics matter, confirm the server can trigger an audit.
3. **Connecting each site when a fleet model is available.** If a Hub-style connection covers the portfolio, per-site OAuth is repeated work that grows with the business.
4. **Skipping the workspace boundary.** Keeping client sites in a separate workspace from internal properties limits the blast radius of a bad instruction.
5. **Treating cache purges as free.** Purging a fleet mid-traffic means every site rebuilds its cache at once. Warm the cache afterwards with the preloader.
6. **Ignoring the `unreachable` status.** A site listed but unreachable will fail silently inside a fan-out call — a partial success is not a success.

## Frequently Asked Questions

**Which should I choose if I only have one site?**
If you already own a WP Rocket license, its MCP is included and requires no migration. If you are starting fresh, xSpeed's free tier includes MCP access with no license.

**Is WP Rocket's MCP read-only?**
No. Its marketing page describes MCP as a read layer, but the 3.23 release post confirms it can read *and adjust* WP Rocket settings, with a per-change approval gate.

**Can one AI connection manage sites across separate client accounts?**
With xSpeed, yes — cross-workspace switching shipped in the August 2026 Hub release. Every site-scoped tool takes an optional `workspace` argument. WP Rocket has no documented equivalent.

**Do I have to give an AI write access?**
No. Both support read-only usage. xSpeed gates scope at consent time; WP Rocket gates each individual change.

**How long does an external speed test take?**
Up to about two minutes, because it runs a genuine PageSpeed Insights or GTmetrix audit rather than reading a cached number.

**Can the AI break my site?**
It can change settings, which is why scope and backups matter. `optimize_site` mitigates this specifically: it verifies the page after each change and reverts anything that measures worse.

**Does either work with ChatGPT as well as Claude?**
MCP is an open standard, so any MCP-capable client works. WP Rocket documents Claude and Codex; xSpeed's Hub endpoint speaks streamable HTTP and works with any compliant client.

**What happens when I add a new site?**
With xSpeed, connect it to the Hub and it appears in the existing conversation — nothing changes in the AI client. With WP Rocket, connect that site individually.

**Is there a free way to try this?**
Yes. xSpeed Cache's free tier includes MCP through the Hub, and a Hub account is free.

**What if my host blocks the connection?**
WP Rocket documents "Couldn't reach [connector]" errors when a host blocks Anthropic IP ranges. The same class of firewall rule affects any MCP server; allowlisting the client's IPs resolves it.

## Conclusion: Which One Fits Your Setup

Both plugins arrived at the same conclusion in 2026 — performance work is a good fit for AI agents, because it is measurable, repetitive, and mostly mechanical. They diverge on scale.

| Your Situation | Better Fit | Why |
|---|---|---|
| One site, already on WP Rocket | WP Rocket MCP | Included; no migration |
| One site, starting fresh | xSpeed Cache MCP | Free tier includes MCP |
| 5–25 sites | xSpeed Cache MCP | One connection, fan-out calls |
| Agency with client accounts | xSpeed Cache MCP | Cross-workspace switching |
| Maximum caution on changes | WP Rocket MCP | Per-change approval gate |
| Want measured, self-reverting optimization | xSpeed Cache MCP | `optimize_site` closed loop |

If you manage one site, the choice is largely about which plugin you already run. If you manage a portfolio, the connection model is the decision — and it is the one that compounds, because it is the only difference that gets worse as you grow.

**Related reading**

- [How to Connect Claude to Every WordPress Site You Own](/blog/connect-claude-to-every-wordpress-site/) — the four ways to wire an assistant to a fleet, including the two non-xSpeed paths
- [10 Best WordPress MCP Servers in 2026](/blog/best-wordpress-mcp-servers-2026/) — the whole category ranked on install data
- [9 Best WP Rocket Alternatives in 2026](/blog/wp-rocket-alternatives-2026/) — if the MCP question is secondary to the caching one

[Connect your first site to xSpeed Hub](/docs/connecting-to-xspeed-hub) — the free tier includes MCP access, and the [MCP tool reference](/docs/mcp-tool-reference) documents all 26 tools.