Give Codex access to your stores.
Checked against official docs on .
Use Codex for a real store check as well as a coding task. Connect the hosted Store MCP endpoint directly, without building a custom commerce integration into your project.
Connect Store MCP to Codex
- Connect an available store in Store MCP before configuring Codex.
- Run the add command below in your terminal. Use a different server name if store is already configured; do not overwrite another connection.
- Run codex mcp login store and complete the browser sign-in. Select the intended stores and View only permissions.
- Run codex mcp list to confirm the saved server. In the Codex terminal interface, /mcp shows connection information.
- Ask Codex to use Store MCP to list your stores, then inspect one known listing before permitting changes.
Run in your terminal
codex mcp add store --url https://store-mcp.com/mcp
codex mcp login store
codex mcp listEquivalent config.toml server entry
[mcp_servers.store]
url = "https://store-mcp.com/mcp"Use the CLI command or add the equivalent entry, not both as duplicate servers. The URL is public configuration, not a credential. Keep authorization tokens out of your repository.
Authorize in your browser. Never paste store passwords or tokens into chat.
Verify your connection
Before you start
You need an available connected store, an eligible Codex account and permission to add a remote MCP connection. Start with View only access to one selected store.
You’re done when…
stores.list returns only your authorized stores. A known listing matches its title and SKU in the provider dashboard. Connect AI shows the grant and Activity records the read.
If the first read fails
Do not enable write access to fix a failed read. Check the account, provider connection and selected store scope. A saved URL is not sufficient verification. Troubleshoot the connection.
A new live Store MCP authentication test in this client has not been performed. Published setup references do not imply directory approval.
Try your first requests in Codex
Name the store and review proposed changes. Examples do not create automatic workflows.
Use Store MCP to list the stores Codex can access. Do not make changes.Show orders needing attention, grouped by store, and explain any coverage limits.Review this listing and suggest a clearer title. Wait before updating it.Start with one store
Free to start with View only access. Compare plans and limits.
Questions before you connect?
Is this the same setup as a ChatGPT web app?
No. This guide configures MCP directly in Codex. ChatGPT web uses its own app connection flow and does not read a local Codex configuration file.
Where is the configuration saved?
Codex uses ~/.codex/config.toml. Trusted projects can also have .codex/config.toml. Merge the server entry into existing configuration instead of replacing the file. The CLI, IDE and desktop surfaces share Codex-host configuration.
What should I check after connecting?
Ask the AI to list your stores, confirm their names and read one known listing or order. A saved URL is not proof of a working connection. Connect AI and Activity in Store MCP show grants and recorded tool use.
Why can it read a store but not make a change?
The Free plan is read-only for marketplace operations. Changes also need write permission, access to that store and a supported provider operation. Approval alone does not grant missing permissions.
Official references and setup availability
Documentation checked 2026-09-21. Menu labels and account eligibility can change. References do not imply a marketplace listing, endorsement or completed production acceptance.
Put your store data to work.
Start with the access you choose.