"Connect Shopify to Codex" hides three distinct jobs: development documentation, customer-facing storefront actions, and merchant-admin operations. Treating them as one connection can send an agent to the wrong store or give a read-only task write privileges it never needed.
Draw the boundary first
Shopify's Dev MCP server gives a compatible development environment access to current developer resources. It runs locally without merchant authentication. It does not by itself grant access to a store's private orders, products, or live theme. Storefront MCP is for shopper-facing experiences; merchant operations need an authorized Admin API, CLI, installed app, or a controlled wrapper.
For Codex CLI, Shopify currently documents this MCP entry:
[mcp_servers.shopify-dev-mcp]
command = "npx"
args = ["-y", "@shopify/dev-mcp@latest"]
Add it to an appropriate Codex configuration, restart the client, and verify the server appears. That is a documentation connection, not a merchant-data test. Do not paste store secrets into the config or a prompt.
Make a store registry before granting access
For each brand, keep a private mapping with: human-readable brand, immutable shop identifier, environment (production/preview), timezone, currency, allowed operations, OAuth/app identity, and approved scopes. The agent should resolve the brand to an exact shop before running tools. A prompt such as "update our summer collection" is insufficient when multiple stores are connected.
Use separate tools and approval rules for read and write:
| Task | Minimum first test | Write gate |
|---|---|---|
| Analyze orders | Verify shop identity, then aggregate a small completed date range | None for read-only analysis |
| Review product content | Read exact product and current fields | Show proposed diff, target store, and request approval |
| Change theme | Confirm development or preview theme identity | Test preview, then authorize a distinct production step |
Scopes and Codex approvals are different controls. Shopify access scopes determine what an app can do; the agent's workflow decides when it may do it. Customer and order data may be protected; prefer aggregates where individual records are unnecessary.
A safe first run
- Ask a narrow, read-only question for one named store.
- Confirm the returned shop name/handle and expected timezone/currency.
- Check that the requested dates and scopes actually return the necessary fields; missing data is unavailable, not zero.
- For a proposed write, show the exact resource ID, before/after values, and preview destination.
- Apply only after approval, then read back the same resource.
This pattern scales to multiple stores by repeating identity checks per connection, not by sharing one credential or assuming the last-used store. Nexscope's commerce-data APIs are a separate research input, not a substitute for Shopify merchant authorization or the shop's own order facts.
Next step: Explore the Nexscope Ecommerce MCP Map →
Adapted from How to Use Shopify MCP With Codex for One or More Stores. Disclosure: Drafted and fact-checked with AI tools against the linked Shopify documentation. No live merchant connection is claimed.
Top comments (0)