How to Connect StoreSEO MCP to Grok Bot

Grok Bot is xAI’s product for Bots you keep around: AI teammates with names, jobs and context that builds up over time. According to xAI’s documentation, all your Bots share one persistent cloud computer with a browser, a filesystem and a terminal, which runs in Cursor’s cloud, so work can continue while your device is closed. It runs in desktop and mobile apps and is included with paid individual Cursor plans, Cursor Teams, or a linked SuperGrok subscription.

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

Before You Start

• Server URL: https://mcp.storeseo.com/mcp
• Sign-in: xAI’s documentation says a custom remote HTTPS server uses the Bot’s own credential, or each person’s sign-in when the server uses OAuth. StoreSEO uses OAuth: you pick your Shopify store in the browser and approve access.
• 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 Grok Bot

Step 1: Ask your Bot to add StoreSEO

In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI’s documentation says a plugin added from your own chat is personal and account-wide, so every Bot on your account can use it. Complete the StoreSEO sign-in when the browser opens: pick your Shopify store and approve access.

Add a custom remote HTTPS MCP server called StoreSEO with the URL https://mcp.storeseo.com/mcp and sign me in.

Step 2: Attach it and check it works

In a chat, type @ to attach the StoreSEO connector to the task, then ask this to confirm the connection.

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

Other Ways to Connect

Option: Add it to a Team Bot from the Setup panel

For a Team Bot, only its owner can change the setup, and the change reaches every teammate. The owner adds the plugin from the Plugins card in the Bot’s Setup panel, choosing a custom MCP server over remote HTTPS, with this URL.

https://mcp.storeseo.com/mcp

Check the Connection

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

• Use @StoreSEO to find my lowest-scoring products and tell me what is wrong with each.
• Which images in my store have no alt text? Preview alt text for five of them with @StoreSEO.
• Is my llms.txt live and current? Tell me what generating a new one would change before you do anything.
• Use @StoreSEO to show Search Console queries from the last 28 days where we rank between 8 and 20.
• Which of my collections have no meta description? Preview one for the weakest and wait for my yes.

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 Grok Bot

• A plugin added from your own chat is personal and account-wide. A Team Bot’s owner adds it from the Plugins card in the Setup panel, and that reaches only that Team Bot’s teammates.
• Be careful with Always allow. It saves a rule for matching actions, so a StoreSEO write tool you always allow no longer stops for your yes in the client, and StoreSEO’s preview-first instruction becomes the only check. Use Ask first rules in Auto-review for apply, generate and publish tools.
• A routine’s Test run performs real work, including calls to connected tools, so run it with safe inputs. Write each routine as report only.
• xAI’s documentation says Grok Bot inherits your team’s Cursor connector policy, a blocked connector shows as Disabled by team admin, and the MCP allowlist is Enterprise only. On a team plan an admin may have to allow the StoreSEO server first.

Run SEO checks on a schedule with a routine

A routine tells one Bot when to run a workflow. Ask the Bot in plain words when to run, what to check, where to report and what it must not do, and it creates the routine and shows its next run. Background routines can run while your laptop is closed, and Routines under the conversation details let you pause one or read its recent runs. Keep a routine to reads and reports. Nobody is there to say yes to a change, and a Test run performs real work, so word it as report only and keep Ask first rules on StoreSEO’s write tools.

Every Monday at 8:00 AM, use @StoreSEO to list my lowest-scoring products, any images without alt text and whether my llms.txt is live. Post a short report in this conversation. Report only and change nothing. If StoreSEO is unreachable, say so instead of reusing last week's data.

Disconnect

Remove the StoreSEO server in Grok Bot, 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 Grok Bot: jobs, prompts and FAQs
• Connect StoreSEO MCP to any AI assistant
• Every AI agent that works with StoreSEO
• xAI: Grok Bot overview (vendor documentation these steps were checked against)
• xAI: Connectors and plugins (vendor documentation these steps were checked against)
• xAI: Team Bots (vendor documentation these steps were checked against)
• xAI: Routines (vendor documentation these steps were checked against)
• xAI: Approvals and security (vendor documentation these steps were checked against)