shopify-multistore-mcp · Free, MIT licence
Ask every client store at once, with each answer naming its store.
shopify-multistore-mcp connects your AI app to several Shopify stores. Each store signs in on Shopify's approval page, without creating apps or copying API keys.
Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and Codex. Not affiliated with Shopify.
30 of 30 right in our mock test, vs 27 for alex-brecher/shopify-multi-store.
Your question
How many orders are unfulfilled in each store?
-
harbour harbour-coffee
.myshopify.com 14 unfulfilled, oldest from Tuesday.
-
tidewater tidewater-swim
.myshopify.com 3 unfulfilled, all from today.
-
northpaper northpaper
.myshopify.com 27 unfulfilled, 9 waiting on stock.
Sample stores and figures shown for illustration.
Shopify's AI connector holds one store at a time.
Even when your stores sit in the same organisation, switching stores in Shopify's connector makes you approve access again.
Shopify's admin switches stores fine; it's only the AI connector that holds one store.
"The Shopify connector supports one store at a time, even when the stores are in the same organization. Switching stores starts a new authorization."
How it works
-
Nine reports across every store.
Ask once and four stores answer together: sales in each store's currency (without test or cancelled orders), unfulfilled orders, low stock to move, and catalogue gaps.
low stock · tidewater is out of coffee beans; harbour has 18.
-
Every answer names its store.
Each reply starts with its store name and address, so client numbers don't mix. Outside the nine reports, your assistant checks Shopify's docs and asks every store.
store: harbour (harbour-coffee.myshopify.com)
-
Changes go to one store.
Edits run on one named store and never retry. Mark any store read-only; creating keys, charging a store or changing app access is blocked outright.
refused · Read-only stores refuse edits; billing and access changes stay blocked.
-
Seven starting prompts in chat.
Apps like Claude Desktop show seven ready-made prompts: morning check, sales, unfulfilled orders, low stock, compare a product, catalogue check and connect a store.
morning check · Pick it and every connected store answers at once.
Compared head to head
Built for agencies: connect client stores without creating apps
We tested shopify-multistore-mcp against alex-brecher/shopify-multi-store across three mock stores (real-store sign-in isn't tested yet). For agencies, it comes down to browser sign-in without copying keys.
- 100%30/30 answers right, vs 27/30 (90%)
- 1median tool call per question, vs 2
- 2.3¢median AI cost per question, vs 3.7¢
- 7.4 smedian time per question, vs 8.8 s
How the two options compare
| What | shopify-multistore-mcp | alex-brecher/shopify-multi-store |
|---|---|---|
| Connecting a store | Approve on Shopify's browser page; no app created | Create a Shopify app and copy secret keys |
| Secret keys | Never reads or copies your store keys | Saves app secrets in your computer's keychain |
| Read-only per store | Yes; any store can refuse all changes | No per-store read-only switch in settings |
| Starter prompts in chat | Seven ready-made starting prompts in the app | None included |
| Shopify API version | Follows newest stable release (2026-10) | Pinned to older 2026-07 release |
| Unfulfilled order counts | Counts partially fulfilled orders as waiting, like admin | Leaves out partially fulfilled orders (0/3 in test) |
| Team and browser access Their lead | Runs on your own computer, not hosted | Hosts for teams; works in ChatGPT and claude.ai |
| Reports and store edits Their lead | 9 reports and one single-store edit tool | 17 reports, guided edits, and 514 admin changes |
Rows 7 and 8 are where alex-brecher/shopify-multi-store leads, along with raw speed in the timing table below.
Measured speed, cost, and install size
31 October 2026: 10 questions x 3 runs (Claude Sonnet 5.5); speed medians across 7 runs.
| Measure | shopify-multistore-mcp 0.3.0 | alex-brecher/shopify-multi-store 2.0.3 |
|---|---|---|
| Questions answered correctly | 30 of 30 (100%) | 27 of 30 (90%) |
| Tool calls per question (median) | 1 | 2 |
| Time per question, end to end (median) | 7.4 s | 8.8 s |
| Model cost per question (median) | 2.3¢ | 3.7¢ |
| Tools in the list sent with every message | 14 (~10k tokens) | 29 (~12k tokens) |
| One store's details, one call | 526 ms | 5 ms |
| Unfulfilled orders across 3 stores | 541 ms | 7 ms |
| Unfulfilled orders across 8 stores | 1.1 s | 12 ms |
| Installed size | 28 MBplus 397 MB of Shopify's CLI and Dev MCP on first start | 32 MB |
Pick alex-brecher/shopify-multi-store for team hosting, browser chat, or broad edits; pick shopify-multistore-mcp for desktop sign-in without app keys.
What this does not show
Both servers ran against three local mock stores instead of live ones, with one model (Claude Sonnet 5.5) on 10 questions our team wrote. You can inspect and re-run everything in evals/.
What it touches, and what it doesn't.
No keys in your files.
Each store signs in on Shopify's approval page; shopify-multistore-mcp never reads or copies access keys. Store data needed for answers still goes to your AI provider.
Newest Shopify tools, checked first.
Updates to Shopify's tools run only after npm integrity, registry signature and start-up checks pass. If a release fails, the last working version keeps running.
One folder per client store.
Each store's sign-in stays in its own folder on your computer, so four stores answer together without clashing. Removing a store deletes its folder.
Open source under MIT licence.
Every line of code is public at fledgeling-co/shopify-multistore-mcp on GitHub. Settings from shopify-multi-mcp (0.1) and StoreRow (0.2) keep working.
- @shopify/cli 5.0.0newest
- @shopify/dev-mcp 1.18.0newest
- npm integritypassed
- registry signaturesverified
- start-up testpassed
Three checks pass before any Shopify tool update runs.
Set it up with one command.
You'll need Node.js 22.12 or newer, a supported AI app (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf or Codex), and permission to approve apps on each Shopify store.
-
Step 1
Run the setup command
Run the command below in Mac Terminal or Windows Command Prompt. It checks Node.js, backs up your AI settings, and adds the connector.
npx -y shopify-multistore-mcp@latest setupSetup finds your AI apps and backs up settings. -
Step 2
Approve each client store
Enter each store's
myshopify.comaddress and approve it on Shopify's browser page. You can also connect stores from chat: "Connect acme.myshopify.com as acme".Approve each store on Shopify's page in your browser. -
Step 3
Restart and ask
Quit and reopen your AI app, then ask your stores. First start downloads Shopify's tools (about 30 seconds).
One question returns answers labelled with each store's name.
Prefer pasting config blocks yourself?
Run this once in a terminal.
claude mcp add shopify-multistore-mcp -- npx -y shopify-multistore-mcp@latestAdd this to the app's MCP settings file.
{
"mcpServers": {
"shopify-multistore-mcp": {
"command": "npx",
"args": ["-y", "shopify-multistore-mcp@latest"]
}
}
}Run MCP: Open User Configuration and add this.
{
"servers": {
"shopify-multistore-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "shopify-multistore-mcp@latest"]
}
}
}Add this to ~/.codex/config.toml.
[mcp_servers.shopify-multistore-mcp]
command = "npx"
args = ["-y", "shopify-multistore-mcp@latest"]If something goes wrong
- If your AI app doesn't see it: fully quit and reopen the app after setup.
- If you see "node: command not found": install Node.js 22.12 or newer from nodejs.org, then restart.
- If a store's session expired: ask your assistant to connect that store again and approve it.
- If the approval page refuses: check with the store owner that your login can approve apps.
Questions
Is this an official Shopify product?
No. shopify-multistore-mcp is an independent open-source tool from fledgeling, and isn't affiliated with or endorsed by Shopify. Each store signs in on Shopify's own approval page using Shopify's published developer tools.
What does it cost?
Nothing; it's free under the MIT licence. Your AI app's own subscription or usage bill is separate.
What do I need?
A computer with Node.js 22.12 or newer, a supported AI app (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf or Codex), a browser to approve each store, and roughly 425 MB of disk space once Shopify's tools download.
Can it change my store?
Only one named store at a time, and edits never retry so nothing runs twice. Mark any store read-only in your config to refuse all edits. Changes creating access keys, charging the store or changing app access are blocked outright.
Does it work in claude.ai in the browser?
No. shopify-multistore-mcp runs on your own computer, so it works with desktop and code apps like Claude Desktop and Cursor, not browser tabs like claude.ai or ChatGPT.
How does it compare with alex-brecher/shopify-multi-store?
Both carry the MIT licence. alex-brecher/shopify-multi-store offers team hosting (claude.ai and ChatGPT), 5 to 12 ms calls, 17 reports and broader edits. shopify-multistore-mcp skips creating apps or copying keys, locks read-only stores, and scored 30/30 in our test.
What if I'm upgrading from StoreRow or shopify-multi-mcp?
Your old settings keep working as they are. shopify-multistore-mcp is the new name for StoreRow (0.2) and shopify-multi-mcp (0.1), and now asks four stores side by side (checking 8 stores dropped from 4.2 s in 0.2 to 1.1 s).
Early release. Tested end to end against Shopify's tools and a schema-checked mock API; nobody has signed in to a real store with it yet. Report issues at github.com/fledgeling-co/shopify-multistore-mcp/issues.
Bring every client store into one chat.
Free, open source, and set up with one command.
Connect your stores