How do I connect ChatGPT dots to xSpeed?
Put your sites in xSpeed Hub once, then add one URL to ChatGPT dots.
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.
2Create the xspeedhub app in ChatGPT
In ChatGPT on the web, turn on Developer mode under Settings, Security and login. Open Plugins, select the plus button and create a developer-mode app named xspeedhub with this URL and OAuth. Click Scan Tools, approve access on the xSpeed Hub page that opens, then click Create. If ChatGPT already has the app, skip this step. On a Business workspace only an admin or owner can turn on developer mode and publish the app.
https://app.xspeedcache.com/xspeed/mcp
3Check that your dot can see it
OpenAI says plugin permissions are shared across dots and ChatGPT. Open your dot's profile, then Customize and Plugins, and check that xspeedhub is there. That screen uses the shared ChatGPT settings, and OpenAI notes the apps available to a dot may differ, so confirm it before you hand over a task.
Dot profile > Customize > Plugins > xspeedhub
4Add a custom rule for site changes
Under Customize, Custom rules, describe the action and pick a behavior: Take action without asking, Take action if pre-approved, Ask before taking action, or Hand off to you. Add a rule that covers purging a cache, changing settings or running a speed test through xSpeed Hub, and choose Ask before taking action.
Customize > Custom rules > xSpeed Hub changes: Ask before taking action
Use xSpeed Hub to list my sites and tell me which ones have page caching turned off. Do not change anything.
You: Every morning, use xSpeed Hub to check my sites and tell me if any has page caching off or a hit ratio under 70%. Report only.
ChatGPT dots: Scheduled for every morning, report only. Running the first check now.
list_sites read-only
→ 3 sites: shop, blog, docs
get_cache_status(site: shop) read-only
→ page cache on, hit ratio 81% in the last 24h
get_cache_status(site: blog) read-only
→ page cache on, hit ratio 46% in the last 24h
get_cache_status(site: docs) read-only
→ page cache on, hit ratio 77% in the last 24h
get_preloader_status(site: blog) read-only
→ preloader idle, last run 9 days ago, 63 URLs not warmed
ChatGPT dots: blog misses more than half its requests and its preloader has not run for nine days. shop and docs are above 70%. Starting the preloader on blog would warm 63 pages. Start it now?
You: Yes, start it.
start_preloader(site: blog) changes site
→ preloader started, 63 URLs queued
ChatGPT dots: Started. Tomorrow's check will show whether blog's hit ratio came back up.
Using it
Prompts to try in ChatGPT dots
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%.
Every Monday, use xSpeed Hub to list sites whose preloader has not run in a week. Report only and change nothing.
With xSpeed Hub, run a mobile PageSpeed test on shop and compare it with the stored score history.
Use xSpeed Hub to check whether Redis is reachable on shop before you suggest the object cache.
With xSpeed Hub, purge the page cache on blog, then start the preloader and tell me how many URLs it queued.
What can ChatGPT dots do with xSpeed?
A guide for each job, written for ChatGPT dots.
Purge the WordPress cache with ChatGPT dots
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 ChatGPT dots
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 ChatGPT dots
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 ChatGPT dots
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 ChatGPT dots
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 ChatGPT dots
See which modules a site has, read their current settings, change them, and turn page caching on or off.
Warm the WordPress cache with ChatGPT dots
Fill the page cache before visitors arrive, for example right after a purge or a deploy.
Set up the Redis object cache with ChatGPT dots
Connect a site to Redis or Memcached so database results survive between requests.
Manage Cloudflare caching with ChatGPT dots
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 ChatGPT dots
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 with your dot
Ask your dot in plain words to run a recurring check. Scheduled runs post in the conversation, and you manage them from Recent activity in the dot's profile or the Scheduled section in ChatGPT, where you can change the repeat schedule, the time and notifications. The Hub has no scheduler for agent prompts, so the timer is the dot's. Nobody is watching a scheduled run, so word it as report only and keep your Ask before taking action rule on xSpeed Hub changes. To stop everything at once, open the ••• menu in the dot's profile and choose Pause.
Every weekday at 8:00, use xSpeed Hub to read the cache status of every site. List any site with page caching off or a hit ratio under 70%, and say which ones you could not reach. Report only: do not purge, toggle, change settings or run speed tests.
Trust and safety
Does ChatGPT dots ask before it changes my site?
In a ChatGPT chat, write actions from a developer-mode app need your confirmation by default, and ChatGPT treats a tool without a read-only annotation as a write. xSpeed Hub's tools carry no such annotation. A dot comes with OpenAI's defaults for which actions need approval, and Custom rules let you set, for an action you describe, Take action without asking, Take action if pre-approved, Ask before taking action or Hand off to you. xSpeed Hub has no confirmation step of its own, so a rule that lets your dot act without asking runs a purge or a settings change as soon as your connection allows writes. Keep xSpeed Hub changes on Ask before taking action. For read-only access, sign in as a Viewer member of the workspace; the connection token's Read-only everywhere switch does not apply, because the app signs in with OAuth.
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
- OpenAI lists dots for Pro users outside the European Economic Area, Switzerland and the UK, for Business Premium, and as a beta on Enterprise, Edu and Healthcare when an admin turns it on. Developer mode has its own plan rules, so check both before you plan around a dot.
- On a Business workspace only an admin or owner can turn on developer mode and publish the app. On Enterprise and Edu an admin grants access first.
- A scheduled task runs with nobody watching. If a custom rule lets your dot take xSpeed Hub actions without asking, a scheduled run can purge or change settings unattended, so keep scheduled prompts to reads.
- Disconnecting the app stops new access but does not delete what your dot already learned from it. OpenAI says deleting that context means resetting the dot.
Reference
What is ChatGPT dots?
ChatGPT dots are OpenAI's always-on agents in ChatGPT. OpenAI's help center says a dot has its own cloud computer, works across the apps you choose to connect, remembers context and keeps making progress between conversations, bringing results back for your review. You create one in the ChatGPT desktop app or on desktop web, and once mobile access reaches your account you can talk to it from the mobile app.
Connected apps give a dot its tools, and OpenAI says plugin permissions are shared across dots, ChatGPT and Codex. So the xSpeed Hub app you register as a developer-mode MCP app in ChatGPT is the connection your dot uses. MCP, the Model Context Protocol, is how that app describes the Hub's caching tools to the model: status, purge, settings, preloader, object cache, Cloudflare and speed tests, for every site in your workspace.
At a glance
- Made by
- OpenAI
- Type
- Always-on agent
- Connects with
- the xspeedhub app from ChatGPT developer mode, shared through Plugins
- Sign-in
- OAuth sign-in
- Last checked
- October 2026
Why use ChatGPT dots with xSpeed?
A cache check that runs itself
Ask your dot for a morning check of every site and it posts what slipped: a site with caching off, a low hit ratio, a preloader that stopped. You read a short report instead of opening each dashboard.
One app for chats and your dot
You register the Hub once in ChatGPT. Plugin permissions are shared, so the same connection serves your chats and your dot, with nothing separate to keep in sync.
Rules for what it may change
Custom rules let you keep purges and settings changes on Ask before taking action, while reads run without a prompt in the dot's own work.
How does ChatGPT dots 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 |
|---|---|---|---|---|
| ChatGPT dots | OpenAI | Always-on agent | the xspeedhub app from ChatGPT developer mode, shared through Plugins | OAuth sign-in |
| ChatGPT | OpenAI | Chat app | Developer mode, then a custom MCP app | OAuth sign-in |
| Codex | OpenAI | Terminal | codex mcp add --url, then codex mcp login | OAuth sign-in or connection token |
| 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?
ChatGPT dots 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