Nous Research

Always-on agent

Hermes Agent + xSpeed

Hermes Agent is the open-source, self-hosted agent from Nous Research, and with xSpeed Hub added as an MCP server it can read cache status, purge, change settings and run speed tests on every WordPress site in your workspace, from the terminal or from the chat apps its gateway serves. You add a few lines of YAML, sign in once, and ask in plain language.

One mcp_servers entry, one URL, every site you connected to the Hub
A tools include list decides which Hub tools Hermes registers, so a reads-only list leaves every write out
Hermes cron can run a report-only xSpeed check on a schedule and deliver it to Telegram, Slack or Discord

Connect Hermes Agent Open xSpeed Hub

Last updated: October 2026

Hermes Agent Always-on agent

xSpeed Hub 29 tools

shop
blog
docs

Connects with an mcp_servers entry in config.yaml, then hermes mcp login. Sign-in: OAuth sign-in or connection token.

How do I connect Hermes Agent to xSpeed?

Put your sites in xSpeed Hub once, then add one URL to Hermes Agent.

1Connect4 steps

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 to config.yaml

Add this entry under mcp_servers. auth: oauth tells Hermes to handle discovery, dynamic client registration, PKCE and token refresh itself. If you edit the file from inside a running session, Hermes reloads its MCP connections with a 30 second timeout, which is too short for a browser sign-in, so finish the entry and then run the login in the next step.

~/.hermes/config.yaml

mcp_servers:
  xspeedhub:
    url: "https://app.xspeedcache.com/xspeed/mcp"
    auth: oauth

3Sign in with hermes mcp login

Run this once. Hermes prints an authorization URL, opens your browser where it can, and waits for the callback on a local loopback port. Sign in to xSpeed Hub and approve. There is no token to paste; Hermes caches the credentials it receives under ~/.hermes/mcp-tokens. On a remote host, paste the redirect URL back into the terminal when Hermes asks, or forward the callback port over SSH.

Terminal

hermes mcp login xspeedhub
hermes mcp test xspeedhub

4Or use a connection token alternative

If you prefer a header, copy the connection token from Connect AI in the Hub (only the workspace owner sees it), add it to ~/.hermes/.env as XSPEED_HUB_TOKEN, and drop auth: oauth from the entry. Hermes resolves the variable when it connects.

~/.hermes/config.yaml

mcp_servers:
  xspeedhub:
    url: "https://app.xspeedcache.com/xspeed/mcp"
    headers:
      Authorization: "Bearer ${XSPEED_HUB_TOKEN}"

1 / 4

2Askexample session

Check it worked

Call xSpeed Hub and list my sites, with the hit ratio of each over the last day.

Example session · Hermes Agent

You: Use xSpeed Hub to check shop's PageSpeed history, then run a fresh mobile test and compare the two.

get_score_history(site: shop) read-only
→ last stored mobile result 61, nine days ago

Hermes Agent: A new test spends some of the shared speed-test allowance and can take about two minutes. Run it on mobile?

You: Yes, run it.

run_speed_test(site: shop, strategy: mobile) uses quota
→ mobile 64, largest contentful paint 3.1 s

Hermes Agent: Mobile reads 64 now, against 61 nine days ago. Scores move between runs, so treat three points as a small change. I can run the benchmark too if you want the cached versus uncached timing.

Using it

Prompts to try in Hermes Agent

Paste one as it is, or change the site name.

Prompt

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

Prompt

With xSpeed Hub, purge the page cache on blog, then start the preloader and tell me how many URLs it queued.

Prompt

Use xSpeed Hub to run a desktop PageSpeed test on docs and compare it with the stored score history.

Prompt

Using xSpeed Hub, check whether Redis is reachable on shop before you turn on the object cache.

Prompt

Ask xSpeed Hub to list the modules on landing and tell me which ones are off, without changing any.

What can Hermes Agent do with xSpeed?

A guide for each job, written for Hermes Agent.

Purge the WordPress cache with Hermes Agent

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 Hermes Agent

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 Hermes Agent

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 Hermes Agent

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 Hermes Agent

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 Hermes Agent

See which modules a site has, read their current settings, change them, and turn page caching on or off.

Warm the WordPress cache with Hermes Agent

Fill the page cache before visitors arrive, for example right after a purge or a deploy.

Set up the Redis object cache with Hermes Agent

Connect a site to Redis or Memcached so database results survive between requests.

Manage Cloudflare caching with Hermes Agent

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 Hermes Agent

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

Hermes has a cron scheduler. It lives in the gateway process, so the gateway has to be running. Each job starts a fresh session and delivers its answer to a target such as Telegram. The Hub has no scheduler for agent prompts, so the timer is Hermes's. A scheduled tick has nobody to answer a prompt. If a rule or the default trust setting pre-approves writes, a scheduled job can run them with no one watching, so keep scheduled jobs to reads unless you mean it, and consider a tools.include list of read tools on the entry. Through the cronjob tool, a job can also set enabled_toolsets to the Hub's toolset, mcp-xspeedhub, so it carries no shell or browser tools.

Terminal

# Create the job
hermes cron create "0 8 * * *" \
  "Use the xspeedhub tools to read the cache status of every site. List any site with page caching off or a hit ratio under 70%. Only read: do not purge, toggle or change anything." \
  --name "xSpeed daily cache report" \
  --deliver telegram

# Check that the scheduler is alive
hermes cron status

Trust and safety

Does Hermes Agent ask before it changes my site?

Hermes Agent

A Hermes server entry has a trust setting. The default, full, adds no approval prompt for that server's tools, and the approvals setting covers dangerous shell commands, not MCP tools. Set trust: untrusted on the xspeedhub entry and Hermes asks before every call to a tool that lacks a readOnlyHint of true. The Hub does not mark its tools that way, so with untrusted every Hub call asks, reads included. To remove writes instead of prompting, set tools.include on the entry to the read tools; the filter takes globs and include wins over exclude. The Hub itself has no confirmation step.

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

Hermes registers each tool as mcp_xspeedhub_ followed by the tool name, for example mcp_xspeedhub_purge_cache. Filters in config use the original tool names, such as purge_cache.
Editing config.yaml from inside a running session starts an automatic MCP reload with a 30 second timeout. Add the entry first, then run hermes mcp login.
Background runs, the gateway and cron never open a browser. When a refresh token stops working, the server is parked until you run hermes mcp login xspeedhub again.

Reference

What is Hermes Agent?

Hermes Agent is an open-source, self-hosted AI agent built by Nous Research. It runs on your own machine or server, keeps memory across sessions, writes its own reusable skills, and can be reached from the command line and from messaging apps such as Telegram, Discord and Slack.

MCP, the Model Context Protocol, is how Hermes reaches services outside your machine. Servers are listed under mcp_servers in config.yaml, and a remote one takes a url. Adding xSpeed Hub that way gives Hermes the Hub's caching tools: status, purge, settings, preloader, object cache, Cloudflare and speed tests, for every site in your workspace.

At a glance

Made by: Nous Research
Type: Always-on agent
Connects with: an mcp_servers entry in config.yaml, then hermes mcp login
Sign-in: OAuth sign-in or connection token
Last checked: October 2026

Why use Hermes Agent with xSpeed?

Filters before the model

tools.include and tools.exclude decide which Hub tools Hermes registers at all. List only reads and the agent has nothing to purge with.

A trust tier per server

Mark the Hub untrusted and Hermes asks before each call. Leave it at the default and Hermes adds no prompt of its own, so choose on purpose.

Cron for routine checks

Hermes cron runs a prompt on a schedule and delivers the answer to your messaging app, which suits a daily cache report.

How does Hermes Agent 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
Hermes Agent	Nous Research	Always-on agent	an mcp_servers entry in config.yaml, then hermes mcp login	OAuth sign-in or connection token
OpenClaw	Open source	Always-on agent	openclaw mcp add with --auth oauth, then openclaw mcp login	OAuth sign-in or connection token
Paperclip	Paperclip	Always-on agent	claude mcp add on the agent's host, or Connect your own MCP server	OAuth sign-in or connection token
NanoClaw	NanoClaw	Always-on agent	ncl groups config add-mcp-server, then ncl groups restart	Connection token
Claude	Anthropic	Chat app	Customize, Connectors, Add custom connector	OAuth sign-in or connection token

Which way should I connect?

Hermes Agent 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

Read the guide →

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

Read the guide →

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

Read the guide →

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

Read the guide →

Frequently asked questions

Add an xspeedhub entry under mcp_servers in ~/.hermes/config.yaml with the url https://app.xspeedcache.com/xspeed/mcp and auth set to oauth, then run hermes mcp login xspeedhub and approve access in the browser. hermes mcp test xspeedhub shows what the server answers.

No. Hermes signs in to the Hub with OAuth and caches the credentials it receives. If you prefer a header, the workspace owner can copy the connection token from the Hub's Connect AI page and reference it from headers through an environment variable in ~/.hermes/.env.

It can. The Hub has no confirmation step of its own, and Hermes adds no prompt for a server marked trust full, which is the default. Set trust to untrusted on the entry to make Hermes ask before Hub calls, filter the write tools out with tools include. For read-only access, send the connection token with Read-only everywhere on, or sign in as a Viewer member.

Yes, through hermes cron. Create a job with a schedule and a prompt, and the gateway runs it in a fresh session and delivers the result to a messaging target. The Hub has no scheduler of its own. Nobody can answer a prompt during a scheduled run, so keep scheduled jobs to reads such as a daily hit-ratio report unless you intend them to write.

The 29 tools of the xSpeed Hub MCP server, registered with the prefix mcp_xspeedhub_. Sixteen only read; thirteen change a site or spend the shared speed-test allowance. A tools include or exclude list on the entry narrows them.

Yes. The xSpeed Cache plugin has its own MCP server at your-site.com/xspeed/mcp, switched on from xSpeed Cache, AI and agents, MCP in wp-admin. The Hub is the better fit once you have more than one site.

Set enabled to false on the xspeedhub entry or remove it from config.yaml. Rotating or disconnecting the connection token in the Hub revokes only clients that send that token, so it does not end an OAuth sign-in; that is removed in Hermes Agent.

Also works with

Documentation

From the blog

Sources checked (5)

Connect Hermes Agent to every site at once.

xSpeed Hub is free and has no site cap. Connect your sites, add one URL, and ask.

Open xSpeed Hub All AI agents