SpritesAdd Sprites to Codex
Available on Anywhere Codex CLI runs — a ChatGPT plan that includes Codex, or an API key. You need a Sprites account with Shopify already connected — the connector acts on that connection, so Codex never handles a Shopify credential.
Add the server
One command writes the entry into ~/.codex/config.toml for you.
Terminalcodex mcp add sprites --url https://mcp.sprites.ai/mcpOr write the config by hand
The same entry in ~/.codex/config.toml, or in .codex/config.toml inside a trusted project when you want the connector scoped to one repo.
~/.codex/config.toml[mcp_servers.sprites] url = "https://mcp.sprites.ai/mcp" auth = "oauth"Sign in
Codex opens a browser for the Sprites consent screen and stores the token locally. Sprites supports dynamic client registration and client ID metadata documents, so there is nothing to pre-register.
Terminalcodex mcp login spritesApprove changes by name
Codex renders results as text, so a pending change comes back written out rather than as a card you can click. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
Pending changeChangeDaily budget $40 → $65Gategate_7f2c…
Official Shopify MCP vs Sprites MCP
Shopify runs its own MCP server at claude.ai/directory/connectors/shopify. Here is what each one covers, so you can pick the one that fits in Codex — or connect both.
Shopify publishes its own connector in Claude’s directory, approved from your Shopify admin. It creates and updates products, collections and inventory, creates percentage-off discount codes, and reads orders, customers and analytics. It cannot edit a live theme, change store settings, issue refunds or cancel orders, and batch status changes stop at 50 items. Separately, every store exposes a public Storefront MCP endpoint for shoppers’ agents.
| Shopify officialclaude.ai/directory/connectors/shopify | Sprites MCPapproval-gated | |
|---|---|---|
| Products and inventory | Creates and updates products, prices, SKUs and stock levels | Reads them; writes product descriptions and SEO fields, never prices or stock |
| Orders and customers | Read only | Not read; Sprites works on the catalogue and content |
| Catalogue-wide SEO | One product at a time; batches stop at 50 | SEO titles and descriptions across every product in one approved run |
| Content and SEO | Product titles and descriptions | Pages, blog posts, product copy and metadata, written for search |
| Before a change applies | Applied when the tool is called, within the access you approved | Drafts and diffs you approve; publishing is a separate click |
If you want to update products, stock and discount codes from a chat, Shopify’s own connector does exactly that. Use Sprites when the job is search and content: SEO fields across the whole catalogue, collection pages and blog posts written to rank, and product copy in the store’s voice — with nothing touching prices or inventory, and every change approved first.
Run the first prompt
Ask Codex this. It routes to a Sprites door, which reads your Shopify account and answers — no account to name, no confirmation to give first.
- With Sprites, which of our products are missing SEO titles or meta descriptions?
- Ask Sprites to list every product in the summer collection with price and inventory.
- Use Sprites to create a collection page for "gifts under $50" and draft it in Shopify.
- Have Sprites rewrite the product descriptions in the summer collection.
- With Sprites, build Meta creative from our three best-selling SKUs.
Run `codex mcp list` and confirm sprites shows as connected.
What Codex can do with Shopify
The same doors, whichever client you are in. Marketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
SEO for every product at once
Missing SEO titles and meta descriptions written across the whole catalogue in one approved run, with any failures listed for a retry.
Read the whole catalogue
Every product, variant and collection, uncapped, and filterable by tag, collection, status or sales channel.
Publish collection pages
Manual or tag-based smart collections with descriptions and SEO fields, proposed for your approval.
Refresh product copy at scale
Descriptions rewritten in the store’s voice, proposed as a set you review before anything lands.
Creative from real products
Ads built from the actual catalogue — price, variant, image — rather than a model's guess at your range.
Store blog without a second tool
Posts drafted into the Shopify blog through the same connector as everything else.
How approvals work here
Codex renders tool results as text, so a Shopify change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
What it reads
- Products, variants, collections, inventory and pricing
- The sales channels each product is published on
- Store pages, blog posts and their SEO metadata
What it can change
- Collection and landing pages, and store blog posts
- Product descriptions, SEO titles, meta descriptions, tags and status
- Never prices or inventory, and nothing without an approval
When it does not work in Codex
Three things go wrong in this client specifically, and each has a one-line fix.
Codex says the tool is not found.
The config was edited while a session was open. Restart Codex — it reads config.toml at startup.
Login loops without ever completing.
The OAuth callback defaults to http://127.0.0.1/callback. If something else on the machine holds that port, set mcp_oauth_callback_url in config.toml and log in again.
Codex says a change was applied and nothing happened in the account.
It was proposed, not applied — that is the design. The approval is waiting in Sprites; open it there and the run continues from where it stopped.
Shopify and Codex: questions
Which URL do I paste into Codex?
https://mcp.sprites.ai/mcp. There is one endpoint and every client uses it — every OAuth grant is bound to exactly that address, so a variant of it will not be honoured.
Can Codex change my Shopify account without asking?
Codex renders tool results as text, so a Shopify change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
Do I need a Shopify API key or developer token?
No. Shopify is connected once inside Sprites through Shopify Admin, and the connector acts on that connection. Codex never sees a credential for it.
Why Codex for Shopify specifically?
Marketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
Is there an official Shopify MCP server?
Several. Every store answers at {shop}.myshopify.com/api/mcp with no authentication, for catalogue search, carts and policies. For merchants, Shopify’s own connector for Claude creates and updates products, collections, inventory and percentage discounts, and reads orders, customers and analytics. Sprites is separate: it works on your catalogue’s SEO and content, and never on prices or stock.
Do I need a Shopify Partner account?
No. Connect a custom app you create in your own Shopify admin and paste its access token, or use the standard OAuth connect. Neither needs a Partner account.
Keep going
The same Codex connector reaches every other channel — nothing else to add.
Shopify, from Codex
Paste one URL, sign in once, and the next Shopify question you ask Codex gets answered from the live account.