Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Shopify Store Sync is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user shopify-store-sync-mcp '--' npx -y shopify-store-sync-mcp
# 2 — ask your agent for something these tools do
# list_stores, list_resource_types, snapshot_store and 9 more
Shopify Store Sync costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Shopify Store Sync as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user shopify-store-sync-mcp '--' npx -y shopify-store-sync-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take 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.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the Shopify stores this server can reach, with their write permissions. Secrets are never returned.
No parameter schema on file.
Describe each resource type that can be snapshotted, diffed and synced, how items are keyed, and which are read by default.
No parameter schema on file.
Read configuration from one store (or a snapshot folder) in portable form (IDs replaced by handles). Returns counts and keys; set full=true to include the data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| full | boolean | no | Include each item's data (can be large). |
Write a store's configuration to a folder as one JSON file per item (sorted keys, no store IDs), ready to commit to git. Use "dir:<path>" as the source of diff_stores or plan_sync to compare or restore from it. Only writes local files, never to Shopify.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | Store alias to read |
| dir | string | yes | Folder to write, inside the snapshot base folder (SYNC_SNAPSHOT_DIR, or the folder the server runs in). Must be empty, new, or an earlier snapshot folder (its item files are replaced). |
Compare configuration between a source and a target: what exists only in the source, what differs (field by field), and what exists only in the target. Either side can be a snapshot folder ("dir:<path>"), e.g. to check whether production drifted from the committed config. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | — |
| target | string | yes | — |
| show_values | boolean | no | Include before/after values for each changed field (default true). |
| limit | integer | no | Max keys listed per section (default 100). |
Build a dry-run plan that would make the target store match the source (a store or a snapshot folder) for the selected resources: creates, updates, conflicts, files to upload and references missing in the target. Nothing is written. Returns a plan_id for apply_plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | — |
| target | string | yes | Store alias to write to |
Show a previously created sync plan. With no plan_id, list recent plans.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | no | — |
| full | boolean | no | Return every op, untruncated. |
Write a reviewed plan to the target store. Refused unless the target has allowWrites=true. For a protected store the person is asked to confirm in the client (or applies from the command line); the assistant can't confirm on their behalf. Re-reads the target first and skips anything that changed…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | — |
| confirm | string | no | Leave empty. Only read when the server runs with SYNC_ALLOW_AGENT_CONFIRM=true (unattended automation); otherwise a protected store is confirmed by the person, not by this argument. |
| only | array | no | Apply only these op seq numbers. |
Read-only comparison of theme configuration between two stores: JSON templates, section groups and settings_data.json (default files: …). Compares the published themes unless theme ids are given. Never writes to a theme. Needs read_themes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | Store alias |
| target | string | yes | Store alias |
| source_theme | string | no | "main" (default) or a theme id |
| target_theme | string | no | "main" (default) or a theme id |
| files | array | no | Theme file patterns, e.g. ["templates/product*.json"] |
| exclude | array | no | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Shopify Store Sync or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | critical | capability blast radius (critical) — client exposure if the model is manipulated | −10 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. critical is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_stores | no tags | |
| list_resource_types | no tags | |
| snapshot_store | sensitive-sourceuntrusted-input | sensitive-source: keyword "read_config"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| export_snapshot | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| diff_stores | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| compare_item | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_sync | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_plan | no tags | |
| apply_plan | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| apply_status | no tags | |
| cancel_apply | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| diff_themes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.11.4. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Shopify Store Sync can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.