How do I connect Codex to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to Codex.
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.
2Add xSpeed Hub and sign in
Add the server with its URL, then log in. The login opens an xSpeed Hub page in your browser; approve access there. There is no token to paste, and Codex keeps the credentials it receives. Start Codex and type /mcp to see the server.
codex mcp add xspeedhub --url https://app.xspeedcache.com/xspeed/mcp codex mcp login xspeedhub
3Keep the Hub's tools on a prompt
Open ~/.codex/config.toml. Set the server to prompt for every tool, then let one read tool run without a question. The tool timeout defaults to 60 seconds, and a PageSpeed test can take up to about two minutes, so raise it.
[mcp_servers.xspeedhub] url = "https://app.xspeedcache.com/xspeed/mcp" default_tools_approval_mode = "prompt" tool_timeout_sec = 150 [mcp_servers.xspeedhub.tools.get_cache_status] approval_mode = "approve"
4Or use a connection token alternative
If you prefer a header to a browser sign-in, copy the connection token from Connect AI in the Hub (only the workspace owner sees it), export it in your shell as XSPEED_HUB_TOKEN and name that variable in config.toml. Codex sends it as a bearer token. Skip codex mcp login in this case.
[mcp_servers.xspeedhub] url = "https://app.xspeedcache.com/xspeed/mcp" bearer_token_env_var = "XSPEED_HUB_TOKEN"
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off.
You: I pushed new theme CSS to staging this morning. Using xSpeed Hub, did the mobile PageSpeed score move since the last stored run?
get_score_history(site: staging) read-only
→ 3 stored runs; latest mobile 58, 8 days ago
run_speed_test(site: staging, strategy: mobile) uses quota
→ mobile 61 after about 90 s
Codex: Mobile went from 58 to 61 since the last stored run. That is inside normal run-to-run variation, so I would not call it an improvement yet. A second run would tell us more. Want me to run one?
You: Not now. Just put the numbers in the commit message.
Codex: Added to the commit message: mobile 58 stored, 61 on a new single run, no claim of improvement.
Using it
Prompts to try in Codex
Paste one as it is, or change the site name.
Use xSpeed Hub to show the cache hit ratio for every site and flag anything under 70%.
I just deployed to shop. Use xSpeed Hub to purge its assets cache only, then check the hit ratio.
With xSpeed Hub, run a mobile PageSpeed test on staging and compare it with the stored score history.
Ask xSpeed Hub to preview what optimize_site would change on docs with a safe pass. Do not apply it.
Using xSpeed Hub, check whether Redis is reachable on shop before you turn on the object cache.
What can Codex do with xSpeed?
A guide for each job, written for Codex.
Purge the WordPress cache with Codex
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 Codex
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 Codex
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 Codex
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 Codex
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 Codex
See which modules a site has, read their current settings, change them, and turn page caching on or off.
Warm the WordPress cache with Codex
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with Codex
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with Codex
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 Codex
Run one action across all of your sites, or a chosen few, and read the result site by site.
Trust and safety
Does Codex ask before it changes my site?
Codex has two layers for shell work: the sandbox mode limits what commands can touch, and the approval policy sets when Codex stops to ask. MCP tools have their own settings. Each server takes default_tools_approval_mode (auto, prompt, writes or approve) and each tool can override it with approval_mode. Codex also asks about MCP calls that advertise side effects or a destructive annotation, but xSpeed Hub's tool definitions do not declare either, so do not rely on that default for the Hub; set the server to prompt. approval_policy never, --yolo and an auto_review reviewer take the human out of the loop. xSpeed Hub has no confirmation step of its own, so an approved or auto-approved write runs as soon as your connection allows writes.
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
- tool_timeout_sec defaults to 60. run_speed_test can take up to about two minutes and run_speed_scan waits about 50 seconds, so raise the timeout or the call can end early.
- A project-level .codex/config.toml applies to trusted projects only. Put the Hub in ~/.codex/config.toml if you want it everywhere.
- approval_policy never and --yolo remove prompts for everything, MCP calls included. For any run you start that way, and for codex exec in scripts or CI, send the connection token with Read-only everywhere on, or sign in as a Viewer member.
- codex mcp login and codex mcp logout work only for streamable HTTP servers that support OAuth. Use the connection token route if you would rather not sign in through a browser.
Reference
What is Codex?
Codex is OpenAI's coding agent. It runs in your terminal as the Codex CLI, in an IDE extension and in the ChatGPT desktop app, reads and edits code, runs commands in a sandbox, and calls tools on MCP servers you add to its config.
MCP, the Model Context Protocol, is how Codex reaches services outside your machine. Adding xSpeed Hub as a streamable HTTP server gives it the Hub's caching tools: status, purge, settings, preloader, object cache, Cloudflare and speed tests, for every site in your workspace. The sandbox's network rules apply to commands Codex runs, not to its connection to an MCP server.
At a glance
- Made by
- OpenAI
- Type
- Terminal
- Connects with
- codex mcp add --url, then codex mcp login
- Sign-in
- OAuth sign-in or connection token
- Last checked
- October 2026
Why use Codex with xSpeed?
Next to the diff
You already review changes in this terminal. Ask Codex to check a site after a push, and put the answer in the commit message or the PR description in the same session.
Approval per server and per tool
One setting puts every Hub tool on a prompt. Per-tool overrides let the read tools run quietly while the writes stay in front of you.
Same setup in three places
The CLI, the IDE extension and the ChatGPT desktop app read one MCP configuration, so you add the Hub once.
How does Codex 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 |
|---|---|---|---|---|
| Codex | OpenAI | Terminal | codex mcp add --url, then codex mcp login | OAuth sign-in or connection token |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in |
| ChatGPT dots | OpenAI | Always-on agent | the xspeedhub app from ChatGPT developer mode, shared through Plugins | OAuth sign-in |
| Claude | Anthropic | Chat app | Customize, Connectors, Add custom connector | OAuth sign-in or connection token |
| Claude Code | Anthropic | Terminal | claude mcp add, then /mcp to sign in | OAuth sign-in or connection token |
Which way should I connect?
Codex 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
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
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
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
Frequently asked questions
Also works with
Documentation
From the blog
- How to Let Claude or ChatGPT Manage Your WordPress Site Speed (via MCP)
- Connecting Claude to a WordPress Fleet in 2026: One of These Five Routes You May Already Be Paying For
- xSpeed Cache MCP vs WP Rocket MCP in 2026: One Connects Once, the Other Once Per Site
- 10 Best WordPress MCP Servers in 2026: 486 in the Directory, Four With More Than Ten Reviews