Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 23/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Shopify Store Sync. Follow https://mcp.popnx.com/i/ussefidder-shopify-store-sync-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Shopify Store Sync for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "shopify-store-sync": { "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Shopify Store Sync tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"shopify-store-sync": {
"command": "npx",
"args": [
"-y",
"shopify-store-sync-mcp"
]
}
}
}Use Shopify Store Sync and tell me what you can do for me, then show me one thing✓ If Claude says it is using Shopify Store Sync or shows a Shopify Store Sync tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SHOPIFY_STORES_FILE Absolute path to your stores.json (store domains and how each one is connected). Defaults to ./stores.json.SYNC_SNAPSHOT_DIR Folder that snapshot exports and dir: sources must stay inside. Defaults to the folder the server runs in.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Shopify Store Sync yet
Shopify Store Sync runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Shopify Store Sync
B · Others in Online shops & payments that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Shopify Store Sync for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user shopify-store-sync -- npx -y shopify-store-sync-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Shopify Store Sync tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user shopify-store-sync -- npx -y shopify-store-sync-mcpYou should see Shopify Store Sync listed as connected
Use Shopify Store Sync and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Shopify Store Sync or shows a Shopify Store Sync tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SHOPIFY_STORES_FILE Absolute path to your stores.json (store domains and how each one is connected). Defaults to ./stores.json.SYNC_SNAPSHOT_DIR Folder that snapshot exports and dir: sources must stay inside. Defaults to the folder the server runs in.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Shopify Store Sync for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "shopify-store-sync": { "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Shopify Store Sync tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Shopify Store Sync and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Shopify Store Sync or shows a Shopify Store Sync tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SHOPIFY_STORES_FILE Absolute path to your stores.json (store domains and how each one is connected). Defaults to ./stores.json.SYNC_SNAPSHOT_DIR Folder that snapshot exports and dir: sources must stay inside. Defaults to the folder the server runs in.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Shopify Store Sync for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "shopify-store-sync": { "type": "stdio", "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Shopify Store Sync tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Shopify Store Sync and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Shopify Store Sync or shows a Shopify Store Sync tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SHOPIFY_STORES_FILE Absolute path to your stores.json (store domains and how each one is connected). Defaults to ./stores.json.SYNC_SNAPSHOT_DIR Folder that snapshot exports and dir: sources must stay inside. Defaults to the folder the server runs in.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user shopify-store-sync -- npx -y shopify-store-sync-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"shopify-store-sync": {
"command": "npx",
"args": [
"-y",
"shopify-store-sync-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"shopify-store-sync": {
"command": "npx",
"args": [
"-y",
"shopify-store-sync-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"shopify-store-sync": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"shopify-store-sync-mcp"
]
}
}
}SHOPIFY_STORES_FILE envSYNC_SNAPSHOT_DIR envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: shopify-store-sync-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account ussefidder, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/ussefidder-shopify-store-sync-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.11.8) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| This one Shopify Store Sync | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Keep your Shopify stores in sync by asking for it.
Compare a dev store with production, see every difference field by field, review a dry-run plan, then apply it. From Claude, Cursor or any MCP client, or straight from the command line.
Get started · What it syncs · Why this tool · Safety · Tested · Roadmap
https://github.com/user-attachments/assets/66a2dfd0-5770-4403-992c-cfe133ea0e9c
Compare, plan, confirm, apply: the full walkthrough, with sound. Every output shown is real, from two sample stores.
Real output of the server's tools on two sample stores.
The store setup that usually gets rebuilt by hand, plus the images it uses. References between items (a size guide pointing at a product, a menu linking to a page) are carried across by handle, so they land on the right item instead of a broken ID.
Details per resource
| Resource | Keyed by | Notes |
|---|---|---|
metafield_definitions | OWNER_TYPE.namespace.key | Name, description, pinning, storefront and customer account access, capabilities, validations. A type change is reported as a conflict, since Shopify can't change a definition's type in place. |
metaobject_definitions | type | Schema, access, capabilities. Fields are added or updated, never removed. Self-referencing definitions are handled. |
pages | handle | Title, body HTML, template, published state. With as_drafts (--as-drafts), new pages are created hidden and existing ones keep their state. |
metaobjects | type/handle | All field values, publish status. References to products, collections, pages and other metaobjects are remapped. A field the source leaves empty is never cleared in the target. With as_drafts, new entries are created as drafts. |
menus | handle | Full item tree (3 levels), including customer account menus. Links to resources are remapped; custom URLs are kept; links to things that can't be matched are left out and reported. Links that only the target menu has are kept, in place, and the plan names them. |
redirects | path | Thousands are fine. |
collections | handle | Title, description, sort order, template, SEO and smart-collection rules (rules on a metafield definition are remapped). Manual collections keep their own product list. A new collection is not published to any sales channel. Manual versus smart is reported as a conflict. |
shop_policies | type | Refund, privacy, terms, shipping and contact policy text. |
products *(opt-in)* | handle | Title, description, vendor, type, category, tags, template, SEO, options, variants (matched by option values; SKU, taxable flag and inventory policy are copied) and images. New products are created as drafts. Prices only with prices: true (--with-prices). On update, the tags, variants, option values and media (images, videos, 3D models) that only the target has are kept, and don't count as differences. Gift cards are skipped. See "What product sync leaves alone" below. |
metafields *(opt-in)* | OWNER/handle/namespace.key | Metafield values on products and collections, landed on the item with the same handle. Reference values are remapped. Filter with namespaces. |
translations *(opt-in)* | locale:Type/handle | Translations of products, pages, collections, metaobjects, menus and policies. Registered against the target's own text, after the content itself is synced. A translated field only the target has is kept. The plan warns when a language isn't added to the target. |
products, metafields and translations can be large, so they're read only when you ask for them (resources: ["products"]). Name what you want and only that is read: exact product handles or prefixes (include: ["linen-shirt", "linen-*"]) for products, and patterns that name their owner (include: ["PRODUCT/linen-shirt/*"]) for metafield values. App-owned (app--…) and Shopify-reserved (shopify--…) data is skipped and listed in the report.
Files and images referenced by any of the above are matched by file name in the target. When one is missing, the plan says so and apply_plan uploads it from the source store.
What product sync leaves alone. Never copied: inventory levels, sales-channel publishing, the status of existing products, barcodes, weight and shipping settings, the image assigned to a variant, videos and 3D models (the target keeps its own), and translations of option names and values. Nothing is ever removed from a target product: a tag, variant or image deleted in the source stays in the target until you remove it there.
Nothing goes live by surprise. New products are drafts and new collections aren't on any sales channel. Pages and metaobject entries copy the published state of the source unless you pass as_drafts; the plan tells you when new ones would be visible right away.
Plenty of Shopify MCP servers read and write *one* store. This one is built for the job *between* stores, where every ID is different:
| Generic Admin MCP servers | shopify-store-sync-mcp | |
|---|---|---|
| Compare two stores | ❌ | ✅ field-level diff |
| Cross-store ID remapping | ❌ you copy raw IDs | ✅ products, collections, pages, blogs, metaobjects, definitions, customer account pages and shop policies |
| Dry run before writing | ❌ | ✅ every write goes through a reviewed plan |
| Detects changes made after planning | ❌ | ✅ re-reads the target and skips anything that drifted |
| Deletes | sometimes | never |
| Production guardrails | ❌ | ✅ writes are off by default; protected stores are confirmed by a person, not by the assistant |
| Audit trail | ❌ | ✅ JSONL log of every write |
Why not just Shopify CLI? The CLI runs one query you wrote, on one store. This tool uses the CLI only to sign in, and does the comparing, ID remapping, ordering, uploads and safety checks for you.
How each safeguard works
allowWrites is false until you set it, per store.apply_plan only runs a plan produced by plan_sync. Plans expire after an hour and their files are removed after a week.protected, the assistant can't supply the confirmation itself. Your client asks you to type the store's domain (MCP elicitation); in a client that can't ask, the plan is applied from the command line with --confirm . The assistant sees store content (page bodies, product descriptions), so this is what stands between a prompt hidden in that content and your production store.~/.shopify-store-sync/audit.log (override with SYNC_AUDIT_LOG).dir:) is validated file by file, can only hold the known resource types, and files are only ever uploaded from Shopify's own file hosts. Over MCP, folders are read and written inside one base folder (SYNC_SNAPSHOT_DIR, or the folder the server runs in).To report a vulnerability, see SECURITY.md.
Most people only need the first option: no app to create. The other two are for scheduled or unattended runs.
npm install -g @shopify/cli
npx shopify-store-sync-mcp connect my-dev-store # read-only npx shopify-store-sync-mcp connect my-staging-store --writes
More about the Shopify CLI sign-in
Each connect opens Shopify in your browser; click Install to approve. It asks for read-only scopes unless you pass --writes (or the store is configured with "allowWrites": true), then prints the line to add to stores.json:
{ "stores": { "my-dev-store": { "domain": "my-dev-store.myshopify.com", "auth": "shopify-cli" } } }
Requests then run through shopify store execute, Shopify CLI's supported command, using the sign-in it saved. Each request starts Shopify CLI (about a second), so a full diff takes tens of seconds instead of one or two with an app. That sign-in belongs to you and expires after a while; when it does, the tool says so and you run connect again. Because of that, use option