SpritesAdd Sprites to Cursor
Available on Any Cursor plan that allows MCP servers, on desktop and on Cursor web agents. You need a Sprites account with Shopify already connected — the connector acts on that connection, so Cursor never handles a Shopify credential.
Write the config
Put the entry in ~/.cursor/mcp.json to have Sprites available in every project, or in .cursor/mcp.json inside one repo to scope it there.
~/.cursor/mcp.json{ "mcpServers": { "sprites": { "url": "https://mcp.sprites.ai/mcp" } } }Or add it from the UI
Cursor lists MCP servers under Customize in the sidebar; adding one there writes the same file.
CursorCustomizeMCPNew MCP serverSign in
Cursor finds the Sprites authorization server from the endpoint's protected-resource metadata, registers itself, and opens a browser for the consent screen. Desktop completes on http://localhost:8787/callback and web agents on cursor.com; both are pre-registered, so there is nothing to allowlist.
Spriteswants access on behalf of Cursor- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelKeep it in the repo, not in your dotfiles
A project-scoped .cursor/mcp.json is worth committing: every teammate who opens the repo gets the same connector and signs in as themselves. The file holds a URL and nothing else — the token is per person and never touches the config.
Run the first prompt
Ask Cursor 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.
Open Cursor Settings → MCP and confirm sprites is listed as connected with its tool count.
What Cursor can do with Shopify
The same doors, whichever client you are in. The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
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
Cursor 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 Cursor
Three things go wrong in this client specifically, and each has a one-line fix.
The Connect button does nothing and no request is made.
A known Cursor issue on some builds. Update Cursor, then remove and re-add the server; if it persists, restart Cursor with the config already in place so the connection is made at startup.
Cursor authenticates but every call comes back unauthorized.
The token was issued for a different address. Delete the server entry, restart Cursor, and re-add it with the exact endpoint above — every grant is bound to that one URL, so a variant of it will not be honoured.
The agent invents ad-platform tools instead of calling Sprites.
Name it: "use Sprites to…". Cursor ranks its own tools first, and a generic phrasing loses to the built-in search.
Shopify and Cursor: questions
Which URL do I paste into Cursor?
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 Cursor change my Shopify account without asking?
Cursor 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. Cursor never sees a credential for it.
Why Cursor for Shopify specifically?
The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
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 Cursor connector reaches every other channel — nothing else to add.
Shopify, from Cursor
Paste one URL, sign in once, and the next Shopify question you ask Cursor gets answered from the live account.