Run Your Shopify SEO from Codex
Codex is OpenAI's coding agent, which runs in your terminal, in an IDE extension and in the ChatGPT desktop app. Connected to StoreSEO, it reads your store's SEO scores, previews optimized content and applies what you approve from the session where you already work on your theme.
- codex mcp add, then codex mcp login
- One config.toml shared by the CLI, the IDE and the desktop app
- Per-tool approval modes you can set from config.toml
Last updated: October 2026
-
You: Is my llms.txt live and up to date? If it needs a rebuild, tell me what that does first.
- storeseo_start read-only
- storeseo_get_llms_txt_status read-only
-
Codex: Your settings changed since the last generation, so a rebuild is due. Generating writes llms.txt into your live theme and Shopify Files and spends AI credit. Run it?
-
You: Yes, run it.
- storeseo_generate_llms_txt needs approval
- storeseo_get_llms_txt_status read-only
-
Codex: The new version is generated and live at your /llms.txt address. Want me to check agents.md next?
StoreSEO is the AI SEO Agent for Shopify merchants — a Shopify app that optimizes your store for Google and gets it cited by ChatGPT, Gemini, Claude and Perplexity.
5.0/5 from 750+ Shopify reviews
How do I connect Codex to StoreSEO?
- 1
Add StoreSEO to Codex
Run this in any terminal. It writes a [mcp_servers.storeseo] table to ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app all read.
Terminalcodex mcp add storeseo --url https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Run the login command. Your browser opens: pick your Shopify store and approve access. Then run codex mcp list, or type /mcp inside Codex, to confirm storeseo is there.
Terminalcodex mcp login storeseo codex mcp list
- 3
Or write it in config.toml Optional
If you would rather edit the file, add this table to ~/.codex/config.toml, or to .codex/config.toml in a trusted project. In the desktop app or the IDE extension you can add the same URL under MCP servers, Add server, Streamable HTTP.
TOML[mcp_servers.storeseo] url = "https://mcp.storeseo.com/mcp"
- 4
Or connect with an access token Optional
Generate a token in StoreSEO under Settings, AI Toolkit, export it as STORESEO_TOKEN in your shell, and point config.toml at that variable. Codex sends it as an Authorization Bearer header, so the token never sits in the file.
TOML[mcp_servers.storeseo] url = "https://mcp.storeseo.com/mcp" bearer_token_env_var = "STORESEO_TOKEN"
Sign-in
Codex signs in with OAuth: run codex mcp 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 let config.toml read it from an environment variable.
Check it worked
Use StoreSEO to show me my store's SEO score breakdown.
What is Codex?
Codex is OpenAI's coding agent. It runs as a command-line tool, as an IDE extension and inside the ChatGPT desktop app, reads the repository you start it in and works through multi-step tasks by calling tools.
It stores MCP servers in config.toml, by default ~/.codex/config.toml, with one [mcp_servers.name] table per server, and the CLI, the IDE extension and the desktop app share that file. A remote server needs a url, and Codex supports OAuth with dynamic client registration, which you start with codex mcp login, or a bearer token read from an environment variable.
Each server can carry its own approval settings: a default mode of auto, prompt, writes or approve, tool allow and deny lists, and per-tool overrides. The writes mode prompts for any tool that is not marked read-only.
Why use Codex with StoreSEO?
One setup, three places
Add StoreSEO once and the terminal, the IDE extension and the ChatGPT desktop app all see it, because they read the same config.toml.
Approvals that match the tools
StoreSEO marks its read tools read-only, so setting the server's approval mode to writes lets reads run and stops for every tool that can change your store.
SEO and theme in one task
Ask Codex to audit the store and then fix the template that causes the problem, so the finding and the change sit in the same session.
Good to know
- The Codex docs show codex mcp add for local commands, and the --url form appears in the OAuth section. If your version rejects it, use the config.toml table instead.
- A project-level .codex/config.toml only loads in trusted projects. Use ~/.codex/config.toml for StoreSEO in every project.
- Set the server's default_tools_approval_mode to writes or prompt, not approve. Approve skips the prompt, and then the confirmation StoreSEO asks for in chat is the only check.
- Codex waits 60 seconds for a tool to finish by default. Content generation can take longer, so raise tool_timeout_sec for the storeseo server if a generation times out.
What can you ask Codex to do in StoreSEO?
Use StoreSEO to list products scoring under 50 and preview better meta for the first five.
Is my agents.md live? If it is the Shopify default, tell me what generating a custom one will publish.
Which images have no alt text? List the ten heaviest first.
Show me my Search Console queries for the last 28 days, grouped by page.
Check which schema types are enabled and tell me what Product schema would add.
Codex guides by job
Each guide covers one StoreSEO job end to end in Codex: setup, prompts, an example session, the rules and the limits.
Which way should you connect?
MCP server with OAuth
- Best for
- Claude, ChatGPT and any client that supports remote MCP sign-in
- Sign-in
- Pick your store in Shopify and approve once
- What you get
- All 44 tools, scoped to the store you approved
MCP server with an access token
- Best for
- Terminal agents and editors, or any client without OAuth
- Sign-in
- Generate a named token in Settings, AI Toolkit and send it as a Bearer header
- What you get
- The same 44 tools; revoke the token in the app to cut access
Shopify Sidekick
- Best for
- Merchants who stay inside Shopify admin
- Sign-in
- Nothing to add: StoreSEO is installed in your store
- What you get
- SEO answers and deep links to the fix page, not the MCP tools
What runs without asking. 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.
Questions
How do I connect Codex to StoreSEO?
Run codex mcp add storeseo --url https://mcp.storeseo.com/mcp, then codex mcp login storeseo. Your browser opens, you pick your Shopify store and approve access, and codex mcp list should show storeseo.
Do I need a StoreSEO API key for Codex?
No. Codex signs in with OAuth and keeps the credentials. A personal access token from StoreSEO under Settings, AI Toolkit is the alternative: put it in an environment variable and set bearer_token_env_var in config.toml.
Where does Codex store the StoreSEO server?
In ~/.codex/config.toml, as an mcp_servers.storeseo table. The Codex CLI, the IDE extension and the ChatGPT desktop app share that file. A project can also carry its own .codex/config.toml if the project is trusted.
Will Codex change my store without asking?
StoreSEO tells the agent to preview first and wait for your yes before it applies content, optimizes images, publishes a file or deletes anything, and that yes is an instruction the agent follows, not a lock on the server. Codex's own approval mode for the server is the hard stop: set it to writes or prompt so tools that can change your store ask first. Reads run straight away.
Which StoreSEO plan does Codex need?
Any active StoreSEO plan, including the free plan, can use the MCP server. Rank tracking is a Pro feature, Google reports need a paid plan with Google connected, and generated content spends AI Content Optimizer credit. See the pricing table for current plans.
Does the ChatGPT desktop app work too?
Yes. The desktop app shares Codex's MCP configuration. Add StoreSEO under Settings, MCP servers, choose Streamable HTTP, paste the URL and select Authenticate. If you already ran codex mcp add, it is already there.
How do I disconnect Codex from my store?
Delete the mcp_servers.storeseo table from config.toml, or set enabled to false to keep it but switch it off. Then revoke the connection or the access token in StoreSEO under Settings, AI Toolkit, where every connected app is listed.