# xSpeed Hub MCP

> Connect Claude, ChatGPT, Cursor or any MCP client to xSpeed Hub once, and manage every WordPress site you connected to the Hub.

- Category: AI & MCP
- Updated: 2026-10-06
- Canonical: https://xspeedcache.com/docs/hub-mcp/

---

**Hub MCP URL:** `https://app.xspeedcache.com/xspeed/mcp`

One MCP connection: all your connected xSpeed sites. Sign in with OAuth, or send a connection token in an `Authorization: Bearer` header.

## Choose your AI client

- [Claude](https://xspeedcache.com/docs/hub-mcp-claude/) (Web, desktop and mobile)
- [Claude Code](https://xspeedcache.com/docs/hub-mcp-claude-code/) (Terminal)
- [ChatGPT](https://xspeedcache.com/docs/hub-mcp-chatgpt/) (Developer mode, web)
- [Cursor](https://xspeedcache.com/docs/hub-mcp-cursor/) (Editor)
- [Codex](https://xspeedcache.com/docs/hub-mcp-codex/) (Terminal)
- [GitHub Copilot](https://xspeedcache.com/docs/hub-mcp-vs-code/) (VS Code)
- [Gemini CLI](https://xspeedcache.com/docs/hub-mcp-gemini-cli/) (Terminal)
- [Other MCP clients](https://xspeedcache.com/docs/hub-mcp-other-clients/)

## Which xSpeed MCP do I need?

- **xSpeed Hub MCP** (recommended): One connection for all your connected sites. `https://app.xspeedcache.com/xspeed/mcp`. [Docs](https://xspeedcache.com/docs/hub-mcp/)
- **xSpeed Cache Site MCP**: A direct connection to one WordPress site. `https://your-site.com/xspeed/mcp`. [Docs](https://xspeedcache.com/docs/mcp-server/)
- **xSpeed Scan MCP**: Speed-test any public website. Manages nothing. `https://xspeedcache.com/scan/mcp`. [Docs](https://xspeedcache.com/docs/scan-mcp/)


## Before you connect

- A free xSpeed Hub account at [app.xspeedcache.com](https://app.xspeedcache.com).
- At least one WordPress site running xSpeed Cache, attached to the Hub. See [Connect your sites to xSpeed Hub](https://xspeedcache.com/docs/connecting-to-xspeed-hub/).
- An AI client that supports remote MCP servers. The guides above cover the common ones.

## How it works

Your AI client signs in to xSpeed Hub once. When you ask about a site, the request names it by its handle, such as `blog` or `shop`, and the Hub passes it to the xSpeed Cache plugin on that site. Some requests can name every site at once.

A sign-in gets the access of the workspace member who approved it, so a Viewer's connection can only read. The connection token can be narrowed further: read-only, only some sites, or with chosen tools blocked. See [Scoped AI connections](https://xspeedcache.com/docs/hub-connection-scopes/).

## After you connect

- [How to write prompts for xSpeed Hub](https://xspeedcache.com/docs/writing-prompts-for-xspeed-hub/): name the site, read before you write, and act on every site in one request.
- [The Hub's tools](https://xspeedcache.com/agent/#tools): what each tool reads or changes.
- [Teams, roles and workspaces](https://xspeedcache.com/docs/hub-teams-and-workspaces/): what a Viewer's connection can do.