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…
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 products are profitable after ad cost this month?
- 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 20 worst-converting product descriptions.
- 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.
Profit after ad cost, per product
The join nobody does by hand: store revenue against what Google, Meta and TikTok spent to get it.
Read the whole catalogue
Every product, variant and collection — uncapped, filterable, and grep-ready when you want to work on it.
Publish collection pages
Real pages in the store, with metadata and internal links, arriving as a draft to approve.
Refresh product copy at scale
Descriptions rewritten against what converts, proposed as a set you review before it 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. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
What it reads
- Products, variants, collections, inventory and pricing
- Orders, revenue and sessions
- Store pages, blog posts and their metadata
- The ad spend attributable to each, from the connected ad accounts
What it can change
- Collection and landing pages, and store blog posts
- Product descriptions and page metadata
- Nothing touches the storefront 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. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
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.
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.
Can it change prices or inventory?
No. Pricing and inventory are deliberately out of scope. It reads them, and writes only content: pages, posts, descriptions and metadata.
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.