How to Connect StoreSEO MCP to Kiro

Kiro is an agentic IDE built and operated by AWS. An AI agent works on your project from a chat panel, plans multi-step changes and can call tools exposed through the Model Context Protocol, including remote HTTP servers.

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

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: Kiro handles the browser OAuth flow for remote servers and supports Dynamic Client Registration: pick your Shopify store and approve. To use a StoreSEO personal access token instead, add an Authorization Bearer value under headers in the same entry.
• 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 Kiro

Step 1: Add StoreSEO to your Kiro MCP config

Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.

{
  "mcpServers": {
    "storeseo": {
      "url": "https://mcp.storeseo.com/mcp"
    }
  }
}

Other Ways to Connect

Option: Choose which StoreSEO tools Kiro may run

Optional. autoApprove lists tools Kiro runs without asking, and disabledTools hides tools from the agent. The names here are real StoreSEO read tools. Keep write tools such as apply, generate and update out of autoApprove so Kiro’s own prompt stays as a second check.

{
  "mcpServers": {
    "storeseo": {
      "url": "https://mcp.storeseo.com/mcp",
      "autoApprove": ["storeseo_start", "storeseo_list_resources", "storeseo_get_resource_seo"]
    }
  }
}

Option: Connect with an access token

If you cannot use the browser sign-in, generate a token in StoreSEO under Settings, AI Toolkit and send it in a headers entry. Keep the file out of a public repository when it holds a token.

{
  "mcpServers": {
    "storeseo": {
      "url": "https://mcp.storeseo.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Check the Connection

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

• Use StoreSEO to list my five lowest-scoring products and preview new meta for each.
• Which product images have no alt text? List them before changing anything.
• Is my llms.txt up to date? If not, say what generating a new one will publish and cost.
• Show me Search Console queries for the last 28 days where we rank between 8 and 20.
• Turn on product schema and tell me what that changes before you do 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 Kiro

• A workspace .kiro/settings/mcp.json overrides a user-level entry with the same name, so if the sign-in seems to point at the wrong store, check which file defines storeseo.
• autoApprove with a wildcard would run every StoreSEO tool without Kiro asking, writes included. List individual read tools instead, so Kiro’s prompt stays a second check.
• A token in mcp.json is a secret. Do not commit a workspace file that holds one, and revoke the token in StoreSEO under Settings, AI Toolkit if it leaks.

Disconnect

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