How to Connect StoreSEO MCP to Kimi Code

Kimi Code is Moonshot AI’s terminal coding agent. You start it with the kimi command in a project folder, and it reads and edits files, runs commands, searches the code and fetches web pages while you watch. It runs the Kimi model, and you sign in with /login using either a Kimi Code OAuth account or a Moonshot platform API key.

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

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: Kimi Code signs you in with OAuth: add the server, run /mcp-config login storeseo, pick your Shopify store in the browser and approve. If you prefer a token, generate one in StoreSEO under Settings, AI Toolkit and put it in the server’s headers.
• 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 Kimi Code

Step 1: Add StoreSEO to Kimi Code

Create or edit ~/.kimi-code/mcp.json so every project on your machine can use StoreSEO. For one repository only, use .kimi-code/mcp.json inside it. You can also run /mcp-config in Kimi Code and have it add the server for you.

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

Step 2: Sign in to your store

Start a new Kimi Code session (a server added mid-session registers in the next one), run this command, then follow the browser window: pick your Shopify store and approve access.

/mcp-config login storeseo

Other Ways to Connect

Option: Connect with an access token

If you cannot use a browser sign-in, generate a token in StoreSEO under Settings, AI Toolkit and add it as a header in the same server entry.

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

Check the Connection

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

Run /mcp to confirm storeseo is connected, then ask: Use StoreSEO to show me my store's SEO score breakdown.

What to Ask Kimi Code

• Use StoreSEO to list every product scoring under 50 and preview new meta for the first ten.
• Which product images have no alt text? Write it for my top collection, one image at a time.
• Is my llms.txt up to date? If not, tell me what generating a new one will change before you run it.
• Show me Search Console queries for the last 28 days where we rank between 8 and 20.
• Check the product schema on my store and tell me which products are missing 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 Kimi Code

• A server added while Kimi Code is open does not register until the next session starts, so restart before you run /mcp-config login.
• Kimi Code reads read-only tool calls without asking, but asks for the rest by default. The /yolo and /auto modes and Approve for this session reduce those prompts; keep apply, write and generate tools on ask so the confirmation StoreSEO asks for is not your only check.
• A project file at .kimi-code/mcp.json overrides a user entry with the same name, so a stale storeseo entry in a repository can shadow the one in your home folder.
• Older Kimi CLI builds keep their settings in a different folder than ~/.kimi-code. These steps are for Kimi Code CLI.

Disconnect

Remove the StoreSEO server in Kimi Code, 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 Kimi Code: jobs, prompts and FAQs
• Connect StoreSEO MCP to any AI assistant
• Every AI agent that works with StoreSEO
• Kimi Code CLI: MCP configuration (vendor documentation these steps were checked against)
• Kimi Code CLI: slash commands (vendor documentation these steps were checked against)
• Kimi Code CLI: interaction and approvals (vendor documentation these steps were checked against)
• Kimi Code CLI on GitHub (vendor documentation these steps were checked against)