How to Connect StoreSEO MCP to 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.

This guide connects NanoClaw to the StoreSEO MCP server at https://mcp.storeseo.com/mcp. Once connected, NanoClaw can read your Shopify store’s SEO scores and settings and, when you agree, apply optimized meta, alt text, schema and other SEO changes. For what to ask once you are set up, see StoreSEO for NanoClaw.

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: NanoClaw’s documentation describes no browser sign-in for an MCP server inside the agent’s container, so connect with a personal access token from StoreSEO under Settings, AI Toolkit, sent as an Authorization: Bearer header.
• Plan: The MCP server works on any active StoreSEO plan, including the free plan. A store with no active plan gets a message with a link to choose one in the app.
• Access token (if you need one): create it in the StoreSEO app under Settings, AI Toolkit. Treat it like a password.

Connect StoreSEO to NanoClaw

Step 1: Create a StoreSEO access token

In the StoreSEO app open Settings, AI Toolkit and generate a personal access token. Keep it out of chat messages and out of Git.

Settings → AI Toolkit → create a token

Step 2: Add StoreSEO to your agent’s container

Run this on the machine that hosts NanoClaw, using your agent group’s ID from ncl groups list. The header goes in as a JSON object. NanoClaw may ask an admin to approve the change.

ncl groups config add-mcp-server --id <group-id> --name storeseo \
  --url https://mcp.storeseo.com/mcp \
  --headers '{"Authorization":"Bearer YOUR_TOKEN"}'

Step 3: Restart the agent’s container

The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask for your store’s SEO score.

ncl groups restart --id <group-id>

Other Ways to Connect

Option: Ask Claude Code to wire it into your fork

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

Add the remote MCP server https://mcp.storeseo.com/mcp to my agent as storeseo, authenticated with this Authorization: Bearer token, then restart the agent.

Check the Connection

Start a new session and send this prompt. NanoClaw should call StoreSEO and answer with your store’s real SEO score.

@Andy use StoreSEO to show me my store's SEO score breakdown.

What to Ask NanoClaw

• @Andy use StoreSEO to list my five lowest-scoring products and what is wrong with each.
• @Andy which of my product images have no alt text? Show me the first ten.
• @Andy preview better meta for my best-selling collection and wait for my yes before saving anything.
• @Andy is my llms.txt live? Tell me when it was last generated.
• @Andy show Search Console queries from the last 28 days where we rank between 8 and 20.

How Approvals Work

Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client’s own tool-approval setting is the hard stop.

Things to Know About NanoClaw

• NanoClaw’s documentation describes no browser OAuth sign-in for an MCP server inside the container, so this setup uses a StoreSEO access token. Treat the token like a password: the header is stored in the agent group’s container configuration on your host, so keep that machine and its backups private.
• NanoClaw says secrets belong with its credential gateway rather than in the agent. If you run a gateway, you can hold the StoreSEO token there for mcp.storeseo.com instead of in the header, following NanoClaw’s gateway documentation.
• The server is added per agent group. Add it to each group that should reach your store, and restart that group’s container afterwards.
• NanoClaw needs Docker on your own machine and the setup is yours to maintain. Whether it asks you before a tool runs depends on how your fork and your admins are set up, so the StoreSEO confirmation in the chat may be the only check.

Send a weekly SEO report with a NanoClaw scheduled task

NanoClaw runs a prompt on a cron schedule in the agent’s own session. A scheduled task has no chat attached, so the prompt has to say where to send the result. A scheduled run should be report-only: the prompt asks for reads, because nobody is there to say yes to a write.

ncl tasks create \
  --group <group-id> \
  --name "Monday SEO report" \
  --recurrence "0 8 * * 1" \
  --prompt "Use StoreSEO to report my SEO score breakdown and the five lowest-scoring products, and send it to telegram. Read only: do not preview, apply, generate or delete anything."

Disconnect

Remove the StoreSEO server in NanoClaw, then revoke the connection or the access token in the StoreSEO app under Settings, AI Toolkit, where every connected client is listed.

Related

• StoreSEO for NanoClaw: jobs, prompts and FAQs
• Connect StoreSEO MCP to any AI assistant
• Every AI agent that works with StoreSEO
• NanoClaw on GitHub (vendor documentation these steps were checked against)
• NanoClaw scheduled tasks (vendor documentation these steps were checked against)
• NanoClaw agent templates and MCP servers (vendor documentation these steps were checked against)
• NanoClaw ncl groups commands (vendor documentation these steps were checked against)