How to Connect StoreSEO MCP to OpenCode

OpenCode is an open-source AI coding agent built by the team behind SST, now Anomaly. It runs in your terminal, and also as a desktop and IDE app, and works through tasks by calling its built-in tools and tools from MCP servers.

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

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: OpenCode signs in with OAuth by default: run opencode mcp auth storeseo, pick your Shopify store in the browser and approve. If you prefer a token, generate one in StoreSEO under Settings, AI Toolkit, set oauth to false and send it as a 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 OpenCode

Step 1: Add StoreSEO to OpenCode

Run this from the project that should use StoreSEO, or add —global to make it available in every project. OpenCode writes a remote server entry to its configuration; the equivalent hand-written entry is shown in the next step.

opencode mcp add storeseo --url https://mcp.storeseo.com/mcp

Step 2: Sign in to your store

Remote servers use OAuth by default. Run the auth command, then pick your Shopify store in the browser and approve access. Inside OpenCode, /mcps does the same: select storeseo and sign in. opencode mcp list should then show it as connected.

opencode mcp auth storeseo
opencode mcp list

Other Ways to Connect

Option: Write it in the config

In OpenCode V2 servers go under mcp.servers. Older versions put the server directly under mcp, so use the layout your version documents.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "storeseo": {
        "type": "remote",
        "url": "https://mcp.storeseo.com/mcp"
      }
    }
  }
}

Option: Connect with an access token

Generate a token in StoreSEO under Settings, AI Toolkit, export it as STORESEO_TOKEN, and turn OAuth off for this server so OpenCode sends the header instead.

{
  "mcp": {
    "servers": {
      "storeseo": {
        "type": "remote",
        "url": "https://mcp.storeseo.com/mcp",
        "oauth": false,
        "headers": {
          "Authorization": "Bearer {env:STORESEO_TOKEN}"
        }
      }
    }
  }
}

Check the Connection

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

Use StoreSEO to show me my store's SEO score breakdown.

What to Ask OpenCode

• Use StoreSEO to list every product scoring under 50 and preview new meta for the first ten.
• Which product images have no alt text? Show me the ten heaviest first.
• Is my agents.md live? If it is only Shopify’s default, tell me what a custom one would publish.
• Show me Search Console queries from the last 28 days where we rank between 8 and 20.
• Which schema types are enabled for my store, and what would turning on Product schema add?

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 OpenCode

• OpenCode V2 expects servers under mcp.servers. Older versions put the server directly under mcp, so check the layout your installed version documents before you edit the file.
• opencode mcp add writes to the project configuration unless you pass —global, so a server added without it only exists in that project.
• There is no remove command for MCP servers. To remove StoreSEO, delete its entry from the config, and run opencode mcp logout storeseo to clear the stored sign-in.
• The OpenCode docs describe deny rules for MCP tools but no ask-first mode, so StoreSEO’s own confirmation in the chat is the main check on writes. Deny the write tools by name if you want a client-side stop.

Disconnect

Remove the StoreSEO server in OpenCode, 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 OpenCode: jobs, prompts and FAQs
• Connect StoreSEO MCP to any AI assistant
• Every AI agent that works with StoreSEO
• OpenCode: MCP servers (vendor documentation these steps were checked against)
• OpenCode: MCP servers (earlier docs) (vendor documentation these steps were checked against)