How to Connect StoreSEO MCP to GitHub Copilot

GitHub Copilot is GitHub’s AI coding assistant. In Visual Studio Code, Copilot Chat has an Agent mode that can plan multi-step work and call tools, including tools from Model Context Protocol servers.

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

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: StoreSEO supports OAuth with dynamic client registration, so VS Code can sign you in through the browser: pick your Shopify store and approve access. No token has to sit in mcp.json.
• 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 GitHub Copilot

Step 1: Add StoreSEO to .vscode/mcp.json

Create or open .vscode/mcp.json in your workspace and paste this. VS Code uses a top-level servers key, not mcpServers, and a remote server needs type http.

{
  "servers": {
    "storeseo": {
      "type": "http",
      "url": "https://mcp.storeseo.com/mcp"
    }
  }
}

Step 2: Start the server and sign in

Run MCP: List Servers from the Command Palette, pick storeseo and start it. If it asks you to sign in, pick your Shopify store in the browser and approve access. Then open Copilot Chat in Agent mode, check the tools icon lists StoreSEO and ask this.

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

Other Ways to Connect

Option: Add it from the Command Palette

Run this command, choose a remote HTTP server, paste https://mcp.storeseo.com/mcp and name it storeseo. VS Code asks where to save it: the workspace shares the entry with your team, your user configuration keeps it to yourself.

MCP: Add Server

Check the Connection

Start a new session and send this prompt. GitHub Copilot 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 GitHub Copilot

• Use StoreSEO to list every product scoring under 50 and preview new meta for the first ten.
• Which product images have no alt text? Preview alt text for my top collection.
• Check my schema settings and tell me which theme file renders the product JSON-LD.
• Is my llms.txt live? Tell me what generating one will change before you run it.
• 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 GitHub Copilot

• VS Code uses the servers key in .vscode/mcp.json. The mcpServers key belongs to the portable .mcp.json file at the project root, so copying a Cursor or Claude snippet unchanged will not work here.
• On Copilot Business and Enterprise plans an organization admin must enable the MCP servers in Copilot policy, otherwise the server will not be usable.
• A .vscode/mcp.json committed to the repository is shared with your team. Keep any token out of it and use input variables if you ever add one.
• Keep the apply, optimize, generate and delete tools on VS Code’s confirmation prompt. StoreSEO asks for your yes in the chat, and the editor’s tool confirmation is the hard stop.

Disconnect

Remove the StoreSEO server in GitHub Copilot, 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 GitHub Copilot: jobs, prompts and FAQs
• Connect StoreSEO MCP to any AI assistant
• Every AI agent that works with StoreSEO
• VS Code: add and manage MCP servers (vendor documentation these steps were checked against)
• GitHub Docs: extend Copilot Chat with MCP (vendor documentation these steps were checked against)