Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 23/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Shopify Store Sync。按照 https://mcp.popnx.com/i/ussefidder-shopify-store-sync-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Shopify Store Sync,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "shopify-store-sync": { "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Shopify Store Sync 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"shopify-store-sync": {
"command": "npx",
"args": [
"-y",
"shopify-store-sync-mcp"
]
}
}
}用 Shopify Store Sync 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Shopify Store Sync,或回答中出现 Shopify Store Sync 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SHOPIFY_STORES_FILE 你的 stores.json 的绝对路径(商店域名及各自的连接方式)。默认为 ./stores.json。 SYNC_SNAPSHOT_DIR 快照导出以及 dir: sources 必须位于其中的文件夹。默认为服务器运行所在的文件夹。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Shopify Store Sync
Shopify Store Sync 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Shopify Store Sync 的应用
B · 网店与支付 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Shopify Store Sync,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user shopify-store-sync -- npx -y shopify-store-sync-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Shopify Store Sync 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user shopify-store-sync -- npx -y shopify-store-sync-mcp应能看到 Shopify Store Sync 在列表中并显示已连接
用 Shopify Store Sync 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Shopify Store Sync,或回答中出现 Shopify Store Sync 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SHOPIFY_STORES_FILE 你的 stores.json 的绝对路径(商店域名及各自的连接方式)。默认为 ./stores.json。 SYNC_SNAPSHOT_DIR 快照导出以及 dir: sources 必须位于其中的文件夹。默认为服务器运行所在的文件夹。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Shopify Store Sync,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "shopify-store-sync": { "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Shopify Store Sync 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Shopify Store Sync 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Shopify Store Sync,或回答中出现 Shopify Store Sync 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SHOPIFY_STORES_FILE 你的 stores.json 的绝对路径(商店域名及各自的连接方式)。默认为 ./stores.json。 SYNC_SNAPSHOT_DIR 快照导出以及 dir: sources 必须位于其中的文件夹。默认为服务器运行所在的文件夹。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Shopify Store Sync,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "shopify-store-sync": { "type": "stdio", "command": "npx", "args": [ "-y", "shopify-store-sync-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Shopify Store Sync 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Shopify Store Sync 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Shopify Store Sync,或回答中出现 Shopify Store Sync 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SHOPIFY_STORES_FILE 你的 stores.json 的绝对路径(商店域名及各自的连接方式)。默认为 ./stores.json。 SYNC_SNAPSHOT_DIR 快照导出以及 dir: sources 必须位于其中的文件夹。默认为服务器运行所在的文件夹。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
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 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 ussefidder 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ussefidder-shopify-store-sync-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.11.8)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
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.
| 本项 Shopify Store Sync | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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