How to Connect StoreSEO MCP to Paperclip

Paperclip is an open-source, MIT-licensed platform for managing teams of AI agents at work. You define a goal, hire agents such as Claude Code, Codex or Hermes into an org chart, set budgets and approvals, and follow every task and tool call from one dashboard. It is self-hosted, needs no Paperclip account and starts with npx paperclipai onboard.

This guide connects Paperclip to the StoreSEO MCP server at https://mcp.storeseo.com/mcp. Once connected, Paperclip 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 Paperclip.

Before You Start

Server URL: https://mcp.storeseo.com/mcp
Sign-in: Paperclip runs its agents headless, so nobody is there to click a browser prompt. Sign in once with OAuth in an interactive session as the same OS user that runs the agent, or skip the browser and send a personal access token from StoreSEO under Settings, AI Toolkit as a 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 Paperclip

Step 1: Add StoreSEO to the agent Paperclip runs

Run this on the machine that hosts the agent, as the same OS user the Paperclip heartbeat runs as, from the agent’s working directory. It is the claude_local adapter path, and user scope makes StoreSEO available to every Claude Code agent that user runs.

claude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp

Start claude interactively as that same user, run /mcp, choose storeseo and finish the browser sign-in: pick your Shopify store and approve. Claude Code keeps the credentials, so later Paperclip runs need no browser. Check with claude mcp get storeseo.

/mcp

Other Ways to Connect

Option: Connect with an access token

If the host has no browser, generate a token in StoreSEO under Settings, AI Toolkit and add the server with the token as a header instead of signing in. Keep the token in a Paperclip secret rather than in a file you commit.

claude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Option: Connect it as a Paperclip connector

On the Connectors page choose Connect your own MCP server and paste the URL. Paperclip walks you through the sign-in and lists StoreSEO’s tools so you can set each one to Allowed, Ask first or Off. It shows as an Unverified server, which describes Paperclip’s review, not the connection.

https://mcp.storeseo.com/mcp

Check the Connection

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

List the MCP tools you have access to without calling any of them, then use StoreSEO to show my store's SEO score breakdown.

What to Ask Paperclip

Check my StoreSEO scores and report the five lowest-scoring products on this ticket. Do not change anything.
Weekly review: list products with no meta description and images with no alt text, then summarize what a fix would involve.
Preview better meta for the lowest-scoring product, show me old and new, and wait for my reply before applying.
Pull my Search Console queries for the last 28 days and note the ones ranking between 8 and 20.
Is my llms.txt current? Report its status and tell me what generating a new one would change before running it.

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 Paperclip

The Claude Code adapter runs headless with dangerouslySkipPermissions on by default, which lets the agent use connected MCP tools without asking. Set it to false so a StoreSEO tool that needs approval does not run unattended, or use the Paperclip connector and keep write tools on Ask first.
Paperclip’s action permissions and review queue apply to connectors only. A server added with claude mcp add on the adapter does not pass through them, so the agent’s own settings and StoreSEO’s confirmation are your checks there.
Remote sign-in cannot finish headless. Complete OAuth once in an interactive claude session as the same OS user that runs the heartbeat, or use a token. A 401 after some hours means the refresh failed and you should sign in again.
User scope in ~/.claude.json is shared by every agent that OS user runs, so every Claude Code agent on that host sees StoreSEO. Use a dedicated OS user or a project scope if only one agent should.

Schedule a report-only store review

Paperclip routines fire on a cron schedule or a webhook, create a task and wake the agent you assign. Keep any scheduled StoreSEO run to reads and a written report: nobody is there to say yes, and the Claude Code adapter does not stop to ask by default. Leave applying, generating and publishing for a task you start and approve yourself.

Weekly store review. Use StoreSEO to read my SEO scores, list the five lowest-scoring products and any Search Console drops, and post the findings on this task. Read only: do not preview, apply, generate or publish anything.

Disconnect

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

StoreSEO for Paperclip: jobs, prompts and FAQs
Connect StoreSEO MCP to any AI assistant
Every AI agent that works with StoreSEO
Paperclip: add an MCP server to an agent (vendor documentation these steps were checked against)
Paperclip: Claude Code adapter (vendor documentation these steps were checked against)
Paperclip: connect a custom MCP server (vendor documentation these steps were checked against)
Paperclip: heartbeats and routines (vendor documentation these steps were checked against)
Paperclip (vendor documentation these steps were checked against)

AI ToolkitStoreSEO MCP

← Previous How to Connect StoreSEO MCP to Hermes Agent Next → How to Connect StoreSEO MCP to NanoClaw

Still need help?

Our support team is happy to assist you.

Contact Support