NanoClaw

Always-on agent

NanoClaw + xSpeed

NanoClaw is a small open-source assistant that runs each agent in its own container on Anthropic's Claude Agent SDK and answers in WhatsApp, Telegram, Slack or Discord, and with xSpeed Hub added to an agent group it can read cache status, purge, change settings and run speed tests on your WordPress sites from a chat message. You add one server with the ncl command line, restart the group, and ask with the trigger word.

Ask about your sites from the chat app you already use
One MCP server on one agent group, sent a token you can set to Read-only everywhere
Scheduled tasks post a report-only cache check to a chat

Connect NanoClaw Open xSpeed Hub

Last updated: October 2026

NanoClaw Always-on agent

xSpeed Hub 29 tools

shop
blog
docs

Connects with ncl groups config add-mcp-server, then ncl groups restart. Sign-in: Connection token.

How do I connect NanoClaw to xSpeed?

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

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 your agent group

Copy the connection token from Connect AI in the Hub (only the workspace owner sees it). Then run this on the machine that hosts NanoClaw, with your agent group's ID from ncl groups list. The header goes in as a JSON object, because NanoClaw refuses credentials inside the URL. NanoClaw may ask an admin to approve the change.

Terminal

ncl groups config add-mcp-server --id <group-id> --name xspeedhub \
  --url https://app.xspeedcache.com/xspeed/mcp \
  --headers '{"Authorization":"Bearer <your connection token>"}'

3Restart the group and ask

The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask something that names xSpeed Hub.

Terminal

ncl groups restart --id <group-id>

4Or ask Claude Code to wire it into your fork alternative

NanoClaw is customised by changing your own copy, and its README says to tell Claude Code what you want. Run Claude Code inside your NanoClaw folder and paste this if you would rather not type the commands yourself.

Text

Add the remote MCP server https://app.xspeedcache.com/xspeed/mcp to my agent group as xspeedhub, with an Authorization: Bearer header holding my xSpeed Hub connection token, then restart the group.

1 / 4

2Askexample session

Check it worked

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

Example session · NanoClaw

You: @Andy use xSpeed Hub to purge the page cache on every site. I just changed the footer.

list_sites read-only
→ 4 sites: shop, blog, docs, landing

NanoClaw: That purges the page cache on all 4 sites, and each one serves uncached pages until it warms again. Purge all 4?

You: Yes, all of them.

purge_cache(site: all, type: page) changes site
→ 3 purged, 1 failed: landing was unreachable

NanoClaw: Purged shop, blog and docs. landing did not answer, so its old footer is still cached. Want me to try landing again in a few minutes?

Using it

Prompts to try in NanoClaw

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

Prompt

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

Prompt

@Andy with xSpeed Hub, purge the page cache on blog, then start the preloader.

Prompt

@Andy use xSpeed Hub to read the PageSpeed score history for shop. Do not run a new test.

Prompt

@Andy with xSpeed Hub, check whether Redis is reachable on shop.

Prompt

@Andy use xSpeed Hub to tell me whether the preloader on docs has finished.

What can NanoClaw do with xSpeed?

A guide for each job, written for NanoClaw.

Purge the WordPress cache with NanoClaw

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 NanoClaw

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 NanoClaw

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 NanoClaw

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 NanoClaw

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 NanoClaw

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

Warm the WordPress cache with NanoClaw

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

Set up the Redis object cache with NanoClaw

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

Manage Cloudflare caching with NanoClaw

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 NanoClaw

Run one action across all of your sites, or a chosen few, and read the result site by site.

Post a report-only cache check on a schedule

NanoClaw runs a prompt on a cron schedule in the agent group's own session. A scheduled task has no chat attached, so the prompt has to say where to send the result. The Hub has no scheduler for agent prompts, so the timer is NanoClaw's. Nobody is there to say yes to a write, so keep the prompt to reads and send it through a token with Read-only everywhere on. Pause, resume, cancel or run a task by hand with ncl tasks.

Terminal

ncl tasks create \
  --group <group-id> \
  --name "xSpeed cache report" \
  --recurrence "0 8 * * 1-5" \
  --prompt "Use xSpeed Hub to read the cache status of every site and send a short report to telegram listing any site with page caching off or a hit ratio under 70%. Read only: do not purge, toggle, change settings or run speed tests."

Trust and safety

Does NanoClaw ask before it changes my site?

NanoClaw

Whether NanoClaw asks you before an MCP tool runs depends on how your fork and its admins are set up; its documentation gates adding a server behind approval but describes no per-tool prompt for calls. xSpeed Hub has no confirmation step of its own, so a write runs as soon as the agent calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, which in NanoClaw shows up as a question in the chat. The firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Keep it on for scheduled tasks.

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

The token is stored in the agent group's container configuration on your host. Keep that machine and its backups private, or hold the token in NanoClaw's credential gateway instead, following its gateway documentation.
The server is added per agent group. Add it to each group that should reach your sites, and restart that group afterwards.
NanoClaw needs Docker on your own machine, and the setup is yours to maintain. Whether it prompts before a tool call depends on your fork.
Rotating or disconnecting the connection token in the Hub cuts off NanoClaw and any other client that sends the same token.

Reference

What is NanoClaw?

NanoClaw is an open-source AI assistant that runs agents in their own containers. It is built on Anthropic's Claude Agent SDK and is meant to be small enough to read, so you own a fork of the code and change it to fit what you need rather than editing a settings file.

You talk to it from a chat app such as WhatsApp, Telegram, Discord or Slack, and an agent answers when you use its trigger word. A remote MCP server is added to an agent group's container configuration with the ncl command line, and the group is restarted to pick it up. MCP, the Model Context Protocol, is how xSpeed Hub describes its caching tools, so one server gives that agent status, purge, settings, preloader, object cache, Cloudflare and speed tests for every site in your workspace.

At a glance

Made by: NanoClaw
Type: Always-on agent
Connects with: ncl groups config add-mcp-server, then ncl groups restart
Sign-in: Connection token
Last checked: October 2026

Why use NanoClaw with xSpeed?

Ask from your phone

The chat app you already use becomes the front end. One message from WhatsApp, Telegram, Slack or Discord and the agent asks xSpeed Hub for the answer.

You own the agent

NanoClaw runs on your machine in containers you control. The Hub is one server on one agent group, and you remove it the same way you added it.

A report that arrives on its own

A scheduled task can read every site each morning and post a short cache report to a chat, through a token that cannot change anything.

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

Which way should I connect?

NanoClaw 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

Copy the connection token from Connect AI in xSpeed Hub. Run ncl groups config add-mcp-server with the name xspeedhub, the URL https://app.xspeedcache.com/xspeed/mcp and an Authorization Bearer header holding the token, then restart the group with ncl groups restart. You can also ask Claude Code to make the same change in your NanoClaw fork.

You need the Hub's connection token, which only the workspace owner can see on the Connect AI page. NanoClaw describes no browser sign-in for an MCP server inside its container, so the token is the route here.

It can. Whether NanoClaw prompts before a tool call depends on your fork, and xSpeed Hub has no confirmation step of its own, so a write runs once the agent calls it. The Hub tells the agent to confirm before a write that touches every site. For a firm stop, turn on Read-only everywhere on the token, which makes the Hub refuse every write tool.

Yes. ncl tasks create runs a prompt on a cron schedule. Name the chat destination in the prompt, because a scheduled task has no conversation attached, and keep it read only.

In the container configuration of the agent group you added it to. NanoClaw stores it in its database and writes it to the group's container.json when the container starts, so the server belongs to that group only.

Yes, for the Hub tools that accept every site, such as purge_cache and start_preloader. The Hub returns a result per site, so the agent can tell you in the chat which sites failed.

Remove the server from the agent group with ncl groups config remove-mcp-server and restart the group. To cut access on the Hub side too, rotate or disconnect the connection token on the Connect AI page.

Also works with

Documentation

From the blog

Sources checked (4)

Connect NanoClaw 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