Connect Codex to xSpeed Hub MCP

Steps

1. 1

   Add 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.

   Terminal Copy

   codex mcp add xspeedhub --url https://app.xspeedcache.com/xspeed/mcp
   codex mcp login xspeedhub

2. 2

   Keep 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.

   ~/.codex/config.toml Copy

   [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"

Sign-in

OAuth sign-in or connection token. Run codex mcp login and approve access in the browser; Codex registers itself with the Hub and keeps the credentials it receives. To use the connection token instead, put it in an environment variable and point bearer_token_env_var at it in config.toml.

[mcp_servers.xspeedhub]
url = "https://app.xspeedcache.com/xspeed/mcp"
bearer_token_env_var = "XSPEED_HUB_TOKEN"

Check it worked

Ask Codex this. It only reads, so nothing changes on your sites.

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

A first prompt

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

If something does not work

• 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.