Skip to main content
Glama

Shopify Multi-Store MCP

One MCP server. Every Shopify store.

Query, compare, report, and make guarded updates across Shopify stores from Claude, ChatGPT, Codex, Cursor, VS Code, and other MCP clients.

CI npm version npm provenance Node.js 20+ MCP ready License: MIT

Demo · Quick start · Reports · AI clients · Security

Version 2.0

Run it locally, or host one server for your team: everyone signs in with their own Shopify staff account and connects from Claude, ChatGPT, Codex or any remote MCP client, with Shopify's own staff permissions deciding what each person can do. Guided Admin workflows, ShopifyQL reports, schema validation, and a generic action surface for any Admin mutation are included. See feature coverage and acceptance requirements. Full Shopify ChatGPT parity is not yet verified.

Related MCP server: Shopify MCP Server

See it work

The demonstration uses sample stores and sample data. The server keeps each real store credential separate.

Quick start

Install the server, connect your stores, and run the health check:

npm install --global shopify-multi-store-mcp-server
shopify-multi-store setup
shopify-multi-store doctor

Claude Code users can add the server with one command:

claude mcp add shopify-multi-store -- npx -y shopify-multi-store-mcp-server start

Each store gets a permanent alias and a separate secure credential. Every store operation requires that alias.

What you get

Capability

Result

Multiple active stores

Keep every Shopify store available in one AI conversation.

Cross-store reports

Search products, compare catalogs, find stock gaps, and report fulfillment SLA breaches.

Parallel GraphQL

Run one read-only query across up to one hundred stores.

Guarded mutations

Target one store and pass an explicit confirmation for each update.

Secure credentials

Use macOS Keychain, Windows Credential Manager, or Linux Secret Service.

Portable skills

Guide Claude, Codex, Cursor, and other compatible agents.

This server and Shopify Dev MCP

The two servers solve different problems. Use both when an agent needs Shopify reference material and access to your stores.

Capability

Shopify Multi-Store MCP

Shopify Dev MCP

Primary purpose

Operate connected Shopify Admin stores.

Search Shopify developer resources.

Store data

Read and compare configured stores.

Does not connect to Shopify Admin store data.

Multiple stores

Keep named stores active in one session.

Not designed for store portfolio operations.

Reports

Provide ready-made operations and catalog reports.

Provide developer documentation and API schemas.

Updates

Run guarded mutations against one selected store.

Does not run Admin API updates against your stores.

Authentication

Use separate credentials for each store.

Needs no authentication.

Shopify Dev MCP helps an agent create and examine Shopify code. This server runs the approved operation against the selected store.

Ready-made reports

shopify_report runs one read-only report across selected stores. Set report to one of these:

Report

Purpose

portfolio_snapshot

Summarize products, orders, customers, currency, plan, and store identity.

order_summary

Summarize order values, discounts, tax, shipping, cancellations, and statuses.

customer_growth

Compare new-customer counts across equal periods.

get_product_everywhere

Find one exact SKU or handle across stores.

compare_inventory

Compare inventory quantities for selected SKUs across stores.

low_stock_report

Find low inventory and cross-store transfer opportunities.

compare_prices

Highlight price and compare-at-price differences for exact SKUs.

duplicate_sku_report

Find repeated SKUs inside stores and shared SKUs across stores.

list_unfulfilled_orders

List open fulfillment work across selected stores.

fulfillment_sla_report

Find late unfulfilled orders and show age buckets.

compare_catalog

Compare products by handle, status, vendor, type, and variants.

catalog_gap_report

Find products that are missing or have different statuses.

catalog_health

Find missing merchandising, SEO, media, alt text, and inventory data.

recent_product_changes

List products updated during a selected period.

compare_collections

Compare collection content and configuration by handle.

store_locations

Review location, fulfillment, inventory, and address coverage.

analytics

Run one ShopifyQL query on each store, with a chart hint. Needs read_reports.

To search products across stores, use shopify_search with resource: "products" and stores.

Try prompts like these:

  • “Give me a portfolio snapshot for every connected store.”

  • “Summarize orders and current order values for the last 30 days. Keep currencies separate.”

  • “Show low, zero, and negative inventory across retail and wholesale.”

  • “Show products that are out of stock here but available in another store.”

  • “Find SKU A123 across every store and compare its status, price, and inventory.”

  • “Search every store for products related to protein.”

  • “Show unfulfilled orders older than two days, grouped by age.”

  • “Find products that are active in one store but missing or draft in another.”

  • “Find price differences and duplicate SKUs across these stores.”

  • “Compare inventory for SKU A123 and B456 across retail and wholesale.”

  • “List unfulfilled orders from the last seven days in three stores.”

  • “Audit catalog health and show the products with missing SEO or media data.”

  • “Compare the active catalog and featured collections across these stores.”

Connect an AI client

The server works in clients that support local stdio MCP servers. Agent Skills improve tool selection when the client supports them.

Add the MCP server:

claude mcp add shopify-multi-store -- npx -y shopify-multi-store-mcp-server start

Copy the included skill for personal use:

mkdir -p ~/.claude/skills/shopify-multi-store
cp skills/shopify-multi-store/SKILL.md ~/.claude/skills/shopify-multi-store/SKILL.md

Add this server to the client's MCP configuration:

{
  "mcpServers": {
    "shopify-multi-store": {
      "command": "npx",
      "args": ["-y", "shopify-multi-store-mcp-server", "start"]
    }
  }
}

Add this server to .vscode/mcp.json:

{
  "servers": {
    "shopify-multi-store": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "shopify-multi-store-mcp-server", "start"]
    }
  }
}

Use npx as the command and -y shopify-multi-store-mcp-server start as the arguments.

Copy skills/shopify-multi-store/SKILL.md into the client's skills directory when supported. Clients without skill support still get every MCP tool.

Host it for your team

Local use on your own computer (above) is the default. Hosting is optional: whoever wants a shared server runs one, and their team connects from the AI app they already use, on any plan: Claude (personal custom connector), ChatGPT, Codex, Claude Code, Cursor, VS Code, Gemini CLI, Windsurf, or any MCP client that supports remote servers.

People sign in with their own Shopify staff account, and every call runs with that person's own Shopify permissions: Shopify decides what they can do, with no roles or policy file on the server. Shopify tokens stay on the server, encrypted. Reconnecting is at most once a day and one click for all stores. Every tool call is audited.

Two ways to host, both self-hosted by whoever wants a shared server:

  • Cloudflare Workers: Deploy to Cloudflare Step-by-step in docs/DEPLOY-CLOUDFLARE.md: create a Shopify app, set four secrets, deploy, add the MCP URL in your AI app.

  • Any server: run shopify-multi-store serve (or the included Dockerfile) and share https://<host>/mcp.

See Connect from your AI app for per-client steps, docs/HOSTED.md for setup, and docs/ACTIONS.md for per-user access and the generic action tools.

Store authentication

Method

Command

Best fit

Admin API access token

shopify-multi-store setup

A custom app you already created in the store admin, with its shpat_ token.

Client credentials

shopify-multi-store oauth

A Dev Dashboard app installed on stores in the same Shopify organization as the app.

Authorization code

shopify-multi-store oauth

A Dev Dashboard app installed on a store outside that organization.

Authorization code setup uses http://127.0.0.1:3456/oauth/callback. Add it as an allowed redirect URL first.

The default authorization code scopes are read-only. Grant only the Admin API scopes required for the task.

Connect your first store

Each store needs an alias (lowercase letters, digits and hyphens, such as main) and its permanent *.myshopify.com domain, which the store admin shows under Settings > Domains. The credential depends on how you get Admin API access. Shopify now creates new apps in the Dev Dashboard; custom apps made in the store admin keep working where they already exist.

With a Dev Dashboard app (new setups):

  1. Open the Dev Dashboard (dev.shopify.com), choose Apps > Create app, and name it (for example "Multi-Store MCP").

  2. Create a version. Under access scopes, add the scopes you need. read_products,read_orders,read_inventory,read_locations,read_customers covers the read tools; for everything the tools can do, print the full list with node "$(npm root -g)/shopify-multi-store-mcp-server/scripts/print-scopes.mjs" --full and remove any scope your app is not approved for. For the authorization code method, also add the redirect URL http://127.0.0.1:3456/oauth/callback.

  3. Release the version, then install the app on your store from the Dev Dashboard, approving the scopes.

  4. Copy the app's client ID and client secret from its settings.

  5. Run shopify-multi-store oauth. Choose client-credentials if the store is in the same Shopify organization as the app, otherwise authorization-code (a browser window opens to approve). Enter the alias, the *.myshopify.com domain, the client ID and the client secret. With client credentials the server gets and refreshes tokens itself.

With a custom app created in the store admin:

  1. In the store admin, open Settings > Apps (Apps and sales channels in some admins) > Develop apps and open your app. If your admin still offers it, you can create one there.

  2. Under Configuration, give the Admin API the scopes you need, then install the app.

  3. Under API credentials, reveal the Admin API access token (it starts with shpat_; Shopify shows it once).

  4. Run shopify-multi-store setup and enter the alias, the *.myshopify.com domain and the token.

Then run shopify-multi-store doctor to check every store, and repeat for each further store. Secrets go to the operating system credential store, never to the configuration file.

Manage stores

shopify-multi-store list
shopify-multi-store doctor
shopify-multi-store remove store-alias
shopify-multi-store import /absolute/path/to/stores.json

The import copies credentials into the operating system credential store and preserves configured stores. Delete the old credential file after checking the import.

MCP tools

The server exposes 31 tools.

Tool

Action

shopify_list_stores

List configured store aliases.

shopify_get_shop_info

Read one store's identity.

shopify_check_access

Show granted scopes and which tools or resources would fail, across one or many stores.

shopify_report

Run a cross-store report (see above).

shopify_bulk_export

Export a whole resource (orders, products, variants, customers, inventory by location, collections, draft orders, or your own bulk query) with an optional search filter in one step, and get the JSONL download link and row counts. No pagination or size limit.

shopify_search

List or search products, collections, orders, customers, draft orders, abandoned checkouts, discounts, publications, redirects, pages, blogs, files, metaobjects, metaobject definitions, metafield definitions, markets, marketing events, price lists, locations, themes, delivery profiles, or webhook subscriptions on one store or several.

shopify_get

Read one product, product variants in full, collection, order, order transactions, order refunds, fulfillment orders, fulfillment with tracking, customer with orders, draft order, discount, inventory, metafield set, metaobject, metaobject definition, page, article, theme files, blog articles, uploaded image, webhook subscription, or bulk operation by ID.

shopify_update_prices

Set price, compare-at price and unit cost for up to 250 SKUs on one store or several.

shopify_set_inventory

Set available inventory with compare-and-set protection.

shopify_create_product

Create a product with options, variants, and images.

shopify_update_product

Update product fields (including handle, SEO and collection membership), variants, media, and tags.

shopify_create_collection

Create a manual or smart collection and publish it to chosen channels.

shopify_update_collection

Update a collection and add products to a manual collection.

shopify_create_discount

Create a percentage discount code.

shopify_upload_image

Upload an image to Shopify Files.

shopify_metafields

Set and delete metafields for any owner.

shopify_redirects

Create and delete URL redirects.

shopify_tags

Add and remove tags on a product, order, customer, or draft order.

shopify_update_order

Update order note, email, phone, PO number, additional details, shipping address, and tags.

shopify_update_customer

Update customer name, email, phone, note, tax exemption, and tags.

shopify_create_fulfillment

Fulfill an order's open fulfillment orders, with optional tracking.

shopify_manage

Guided writes by operation: product variants and options; create customer, customer addresses, merge customers; create, complete, update and delete draft orders; cancel, close, reopen or mark an order paid; refund; delete a product or customer; discounts (amount off, percentage, free shipping, buy X get Y; activate, deactivate, delete, add codes); fulfillment tracking and cancel; inventory adjust, move between locations, item update, activate and deactivate; pages, blog articles and blogs; metaobjects and metafield definitions; files (create from URL, update, delete); webhook subscriptions.

shopify_find_actions

Search every Admin API mutation.

shopify_describe_action

Describe one mutation.

shopify_run_action

Run any mutation on one or more stores.

shopify_graphql_query

Run a read-only Admin GraphQL query.

shopify_graphql_query_many

Run one query across several stores.

shopify_graphql_mutation

Change one store after exact authorization.

shopify_graphql_schema

Explore the Admin GraphQL schema.

shopify_validate_graphql_codeblocks

Validate GraphQL without running it.

shopify_search_docs_chunks

Search Shopify documentation.

Read-only operations can run in parallel. Mutations stay isolated to the selected stores.

Every guided write tool defaults to dryRun: true, which returns a before/after (or would-create) preview without changing anything; pass dryRun: false, after the user authorizes the exact store and change, to apply it. The tool then reads the result back. Tags on products, orders, and customers change with addTags and removeTags; replaceTags replaces every tag and the preview lists the tags it would remove. Write results are never dropped for size: large results are trimmed, keeping status, counts, and every item that did not apply.

shopify_manage needs confirm for operations that cannot be undone (every delete action, merge_customers, order cancel, fulfillment cancel, inventory deactivate), and a refund applies only when expectedAmount matches Shopify's suggested refund from the preview.

shopify_graphql_mutation and shopify_run_action refuse denylisted mutations and need confirm set to the mutation name for destructive ones, including mutations that are destructive only because of their arguments, such as a product status of ARCHIVED.

Generic action tools

Three tools reach every Shopify Admin API mutation (523 in API 2026-07), including the 435 without a dedicated tool:

Tool

Action

shopify_find_actions

Search all mutations by keyword and category; flags destructive ones and existing dedicated tools.

shopify_describe_action

Show one mutation's arguments, input fields, payload, a ready-to-edit document, and a scope hint.

shopify_run_action

Run a mutation on 1 to 100 stores, with per-store variables. Dry run by default, resolving every record ID it would touch; destructive mutations need confirm set to the mutation name.

A denylist blocks mutations that mint credentials or change the app's own billing. Request the full scope set with node scripts/print-scopes.mjs --full. See docs/ACTIONS.md for worked examples and what no third-party app can do.

Shopify companion skill

Install Shopify's official shopify skill:

shopify-multi-store install-shopify-skills

The command installs the skill for every supported agent it detects. Pass --agent <name> to select one agent, for example --agent claude-code.

The shopify skill is one skill with a routing table. Its admin topic searches Shopify documentation and validates custom Admin GraphQL operations. Its shopifyql topic covers sales, revenue, order, conversion, and trend analysis. Shopify's toolkit 2.0.0 merged the former shopify-admin and shopify-shopifyql skills into this one skill, and the toolkit's ucp skill (a shopping CLI) is not part of this install.

If Shopify renames the skill again, the command exits with status 1, prints the skills the toolkit ships, and shows the npx skills add command to install one by name. It never reports success after installing nothing.

This server still controls store selection, credentials, execution, and mutation authorization. Shopify's skill scripts send usage telemetry by default.

Set OPT_OUT_INSTRUMENTATION=true to turn off that telemetry.

This integration uses the official Shopify AI Toolkit. It also reflects useful patterns from Shopify Admin Skills.

Read-only mode

Turn writes off for the whole server, for chosen stores, or for chosen people. These are plain settings, not secrets, so the rules stay visible in your deployment config.

Setting

Effect

SHOPIFY_READ_ONLY=true

No writes on any store, for anyone. Write tools are not listed.

SHOPIFY_READ_ONLY_STORES=outlet,wholesale

Nobody can write to those stores.

SHOPIFY_READ_ONLY_USERS=pat@example.com

Pat cannot write anywhere and does not see write tools (hosted server).

SHOPIFY_READ_ONLY_USERS=pat@example.com:wholesale

Pat cannot write to wholesale; other stores follow Pat's Shopify permissions.

The check runs where every Shopify call is sent, so no tool, including shopify_run_action and the raw GraphQL tools, can get around it. A refused write sends nothing to Shopify. Two mutations that change nothing stay allowed: draftOrderCalculate (draft order previews) and bulkOperationRunQuery (exports). shopify_list_stores and the hosted stores page mark read-only stores, and the audit log records refusals as read_only.

Security model

Secrets never enter the main configuration file.

Platform

Credential backend

macOS

Keychain

Windows

Credential Manager

Linux

Secret Service

The configuration stores aliases, domains, API versions, and non-secret OAuth client IDs. Its default path is ~/.config/codex-shopify-multi-store/stores.json.

The codex-shopify-multi-store name, in that path and as the credential store's service name, is a legacy name from the project's first version. It stays so existing installs keep their stores and credentials; it does not mean the server works only with Codex.

Set SHOPIFY_MULTI_STORE_CONFIG to use another configuration path.

  • Never commit access tokens, OAuth client secrets, .env files, or credential-bearing configuration files.

  • Grant only the Shopify Admin API scopes required for the task.

  • Confirm the target store before every mutation.

  • Read SECURITY.md for vulnerability reporting.

Linux credential storage requires a Secret Service provider, such as GNOME Keyring or KWallet.

Other installation options

Run a health check without a global install:

npx -y shopify-multi-store-mcp-server doctor

Install directly from GitHub (npm runs the prepare script, which builds the server):

npm install --global github:alex-brecher/shopify-multi-store

Development

git clone https://github.com/alex-brecher/shopify-multi-store.git
cd shopify-multi-store
npm ci
npm test
npm run test:live
npm pack --dry-run

The live test uses configured stores and performs read-only Shopify Admin API calls.

License

MIT

Read the changelog, contribution guide, security policy, and directory submission guide.

Available Tools

31 tools
shopify_bulk_exportBulk ExportA
Read-only

Export a whole resource from one store in one step, with no pagination or size limit: orders, products, variants, customers, inventory (levels per location), collections or draft orders, with an optional Shopify search filter such as "created_at:>=2026-10-01". Starts a Shopify bulk operation, waits up to waitSeconds, and returns the JSONL download URL (valid 7 days) and row counts; sampleRows also returns the first rows. Large stores can take minutes: call again with action:"status" and the id. resource custom runs your own bulk query. Changes nothing in the store.

Inputs: store (required), id, query, action, +5 more.

shopify_check_accessA
Read-onlyIdempotent

For one or many stores, report the shop identity and granted Admin API access scopes, compare them against every tool's requirement (see src/scope-requirements.ts; tools with several resources or reports are listed as tool:resource), and report missing scopes and which tools would fail. Omit stores to check every configured store.

Inputs: stores.

shopify_create_collectionA
Destructive

Create a manual collection (optional productIds) or a smart collection (ruleSet). Pass publicationIds to publish to explicitly selected channels. Defaults to dryRun:true, which previews the input without creating anything.

Inputs: store (required), title (required), image, dryRun, +5 more.

shopify_create_discountB
Destructive

Create a percentage discount code with an explicit start date and customer audience. Defaults to dryRun:true, which resolves segments and previews the discount without creating it.

Inputs: code (required), store (required), title (required), startsAt (required), +11 more.

shopify_create_fulfillmentA
Destructive

Fulfill the remaining quantities of an order's OPEN and IN_PROGRESS fulfillment orders with optional tracking. notifyCustomer defaults to false. Requires read_merchant_managed_fulfillment_orders and write_merchant_managed_fulfillment_orders (Shopify reports any other missing scope, such as for fulfillment orders assigned to a fulfillment service). Defaults to dryRun:true.

Inputs: store (required), orderId (required), dryRun, trackingUrl, +3 more.

shopify_create_productA
Destructive

Create a product with options, variants and images, and optionally add it to a manual collection. Defaults to status DRAFT and to dryRun:true, which previews the input without creating anything.

Inputs: store (required), title (required), tags, price, +9 more.

shopify_describe_actionDescribe a Shopify Admin ActionA
Read-onlyIdempotent

Full signature of one Admin API mutation: arguments with types, the expanded input object fields (required markers, enum values, descriptions), the payload fields, a ready-to-edit GraphQL document with a default selection, a variables template with the required fields, a scope hint, and whether it is destructive (then shopify_run_action needs confirm set to the mutation name).

Inputs: mutation (required), depth, store, apiVersion.

shopify_find_actionsFind Shopify Admin ActionsA
Read-onlyIdempotent

Search every Shopify Admin API mutation (hundreds of write actions, most without a dedicated tool) by keyword and optional category. Returns each action's name, one-line description, category, whether it is destructive, which dedicated tools already cover it, and a scope hint. Next: shopify_describe_action for the full signature, then shopify_run_action.

Inputs: limit, query, store, offset, +3 more.

shopify_getGet a Shopify RecordA
Read-onlyIdempotent

Read one record by GID from one store. Follow each returned cursor independently. Resources:

  • product: Product details, variants (first/after) and media (mediaAfter). id: Product GID.

  • collection: Collection details, rules and a page of products. id: Collection GID.

  • order: Order, shipping, fulfillment, tracking and a page of line items. id: Order GID.

  • inventory: Inventory by product (id: Product GID) or inventory item (id: InventoryItem GID, pages through locations).

  • metafields: Metafields of any owner (id: owner GID); optional namespace and key.

  • theme_files: Theme file contents. id: OnlineStoreTheme GID; optional filenames, else pages through every file.

  • blog_articles: A blog's articles. id: Blog GID.

  • uploaded_image: Image processing status and CDN URL. id: MediaImage GID.

  • bulk_operation: A bulk operation's status and result URLs. id: BulkOperation GID. Partial exports stay marked incomplete.

  • customer: Customer details, addresses, marketing consent state and a page of orders, newest first. id: Customer GID.

  • draft_order: Draft order with status, totals, addresses and line items. id: DraftOrder GID.

  • variants: Every variant field of a product (price, barcode, tax, inventory policy, weight, cost, origin, HS code, options) with first/after. id: Product GID.

  • order_transactions: An order's payment transactions (authorizations, captures, refunds, voids). id: Order GID.

  • order_refunds: An order's refunds with refunded items, restock status and transactions. id: Order GID.

  • fulfillment_orders: An order's fulfillment orders with status, location, delivery method, holds and line items. id: Order GID.

  • webhook: One webhook subscription of this app. id: WebhookSubscription GID.

  • page: One Online Store page with its HTML body, handle, isPublished, publishedAt and templateSuffix. id: Page GID.

  • article: One blog article with body, summary, author, tags, image, isPublished, publishedAt and its blog. id: Article GID.

  • metaobject: One metaobject: handle, type, displayName, fields (key, type, value, jsonValue), updatedAt, capabilities. id: Metaobject GID.

  • metaobject_definition: One metaobject definition with full field definitions and validations. id: MetaobjectDefinition GID.

  • fulfillment: One fulfillment: status, tracking info (company, number, url), line items, location and createdAt. id: Fulfillment GID (from the order's fulfillments).

  • discount: One discount in full: status, summary, dates, value, minimum requirement, who is eligible, items it covers, combinesWith, usage limits and usage, and the first 20 codes with a code count. id: DiscountNode, DiscountCodeNode or DiscountAutomaticNode GID.

Inputs: id (required), store (required), resource (required), key, +5 more.

shopify_get_shop_infoGet Shopify Store InformationA
Read-onlyIdempotent

Get identity and account information from one named Shopify Admin store. Use this tool before a sensitive change to make sure that the selected store is correct.

Inputs: store (required).

shopify_graphql_mutationChange a Shopify StoreA
Destructive

Run one GraphQL Admin API mutation against one named store. Set confirm to true only after the user authorizes the exact store and change. Destructive mutations (see shopify_describe_action; some are destructive only with certain arguments, such as a product status of ARCHIVED or notifyCustomer true) need confirm set to the mutation name instead, and denylisted mutations are refused, exactly as in shopify_run_action. The result reports each top-level mutation field as applied, rejected, or unknown, and the store as applied, rejected, partial, or unknown; after partial or unknown, retry only the rejected fields in a new document.

Inputs: store (required), confirm (required), mutation (required), variables.

shopify_graphql_queryQuery a Shopify StoreA
Read-onlyIdempotent

Run one read-only GraphQL Admin API query against one named store. Use cursor pagination and request only necessary fields.

Inputs: query (required), store (required), variables.

shopify_graphql_query_manyQuery Multiple Shopify StoresA
Read-onlyIdempotent

Run the same read-only GraphQL Admin API query across multiple named stores in parallel. Each store returns its own success or error result.

Inputs: query (required), stores (required), variables.

shopify_graphql_schemaC
Read-onlyIdempotent

Explore the Admin GraphQL schema for this store's API version.

Inputs: store (required), type_name (required).

shopify_list_storesList Shopify StoresA
Read-onlyIdempotent

List every Shopify Admin store that remains connected to this plugin. On a hosted server in per-user mode, lists only the stores you have connected with your own Shopify account and names the others with a link to connect them. This tool does not expose access tokens.

Inputs: no named parameters.

shopify_manageA
Destructive

Guided writes for one store, chosen by operation. Every operation reads the current state first, defaults to dryRun:true (a preview that changes nothing), never notifies customers unless asked, and reads the result back after a write. Put the operation's fields in input. Operations:

  • webhook: Create, update or delete one of this app's webhook subscriptions (webhookSubscriptionCreate / Update / Delete). Deliver to an HTTPS URL, Google Pub/Sub (pubsub://project:topic) or Amazon EventBridge. A subscription keeps sending store data to its uri until it is deleted, whoever made it, so create, and an update that changes uri, need confirm:"webhook"; delete needs confirm:"delete". create refuses a duplicate topic and uri. The name records who made the change. Shopify shows an app only the webhook subscriptions it created; other apps' subscriptions are not listed. input: {action: create|update|delete, id?, topic?, uri?, format?: JSON|XML, filter?, includeFields?: [...], metafieldNamespaces?: [...], name?}

  • page: Create, update or delete an Online Store page (pageCreate / pageUpdate / pageDelete). body is HTML. update and delete read the page first; update previews current and changes. A handle change on update can leave the old URL redirecting (redirectNewHandle). delete cannot be undone and needs confirm:"delete". seo is not available: Shopify's page input has no SEO fields. input: {action: create|update|delete, id?, title?, body?, handle?, isPublished?, publishDate?, templateSuffix?, redirectNewHandle?}

  • article: Create, update or delete a blog article (articleCreate / articleUpdate / articleDelete). create needs blogId, title and author (a name). body and summary are HTML; imageUrl is a public https URL with imageAlt. update and delete read the article first; blogId on update moves it to another blog. delete cannot be undone and needs confirm:"delete". input: {action: create|update|delete, id?, blogId?, title?, body?, summary?, author?, tags?: [...], imageUrl?, imageAlt?, isPublished?, publishDate?, handle?, templateSuffix?, redirectNewHandle?}

  • blog: Update a blog's title, handle, commentPolicy (AUTO_PUBLISHED, MODERATED or CLOSED) or templateSuffix (blogUpdate). Update only: blogs are not created or deleted here. Reads the blog first; dryRun:true (the default) previews. redirectNewHandle and redirectArticles keep old URLs working after a handle change. input: {id, title?, handle?, commentPolicy?: AUTO_PUBLISHED|MODERATED|CLOSED, templateSuffix?, redirectNewHandle?, redirectArticles?}

  • metaobject: Create, update, upsert or delete one metaobject entry (metaobjectCreate / Update / Upsert / Delete). Reads the definition first and rejects unknown field keys before any write. create: type, optional handle, fields [{key, value}], optional status DRAFT or ACTIVE (publishable types). update: id plus fields and/or status. upsert: type plus handle plus fields. delete: id, needs confirm "delete". input: {action: create|update|upsert|delete, id?, type?, handle?, fields?: [{key, value}], status?: DRAFT|ACTIVE}

  • metafield_definition: Create one metafield definition (metafieldDefinitionCreate); create only. Refuses when ownerType, namespace and key already have a definition. The access scope depends on the owner type (for example write_products for PRODUCT, write_customers for CUSTOMER), so none is checked up front and Shopify rejects a missing one. type is a metafield type name such as single_line_text_field or list.single_line_text_field; validations are {name, value} pairs; pin puts it at the top of the admin page. input: {action: create, ownerType, namespace, key, name, type, description?, validations?: [{name, value}], pin?}

  • draft_order: Edit or delete an existing draft order. update (draftOrderUpdate): any of lineItems (replaces the whole list), customerId, email, note, tags (replaces), shippingAddress, billingAddress, appliedDiscount, shippingLine and reserveInventoryUntil; the preview runs draftOrderCalculate when lineItems change. delete (draftOrderDelete) cannot be undone and needs confirm:"delete". Completed draft orders are refused. No invoice is sent. Create and complete are separate operations. input: {action: update|delete, id, lineItems?: [{variantId?, title?, price?, quantity, sku?, taxable?, requiresShipping?}], customerId?, email?, note?, tags?: [...], shippingAddress?: {firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}, billingAddress?: {firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}, appliedDiscount?: {value, valueType: FIXED_AMOUNT|PERCENTAGE, title?, description?}, shippingLine?: {title, price}, currencyCode?, reserveInventoryUntil?}

  • file: Create, rename or delete files in Content > Files, any content type. create (fileCreate) copies a public HTTPS originalSource URL into Shopify as FILE, IMAGE, VIDEO, EXTERNAL_VIDEO or MODEL_3D, with alt and filename. update (fileUpdate) changes alt and filename. delete (fileDelete, up to 50 ids) cannot be undone and needs confirm:"delete"; it lists the files first. Shopify processes files asynchronously: fileStatus starts as UPLOADED or PROCESSING and becomes READY. Check with shopify_search files or shopify_get uploaded_image. input: {action: create|update|delete, originalSource?, contentType?: FILE|IMAGE|VIDEO|EXTERNAL_VIDEO|MODEL_3D, alt?, filename?, id?, ids?: [...]}

  • fulfillment: Change tracking on a fulfillment (update_tracking, fulfillmentTrackingInfoUpdate) or cancel it (cancel, fulfillmentCancel). Cancel reverses the fulfillment and reopens its items on new fulfillment orders; it needs confirm:"cancel". notifyCustomer defaults to false. Reads the fulfillment first. Needs a fulfillment-order write scope; write_merchant_managed_fulfillment_orders covers fulfillments of merchant-managed locations. input: {action: update_tracking|cancel, id, company?, number?, url?, notifyCustomer?}

  • inventory: Inventory changes beyond shopify_set_inventory. adjust: up to 100 relative changes {inventoryItemId or sku, locationId, delta} (inventoryAdjustQuantities), each checked against the current quantity. move: items {inventoryItemId or sku, quantity} from fromLocationId to toLocationId, taken from available stock, done as one atomic adjust (inventoryMoveQuantities cannot cross locations). move_state: move quantity between states at one location, such as available to damaged (inventoryMoveQuantities; needs referenceDocumentUri). update_item: tracked, cost, countryCodeOfOrigin, harmonizedSystemCode, provinceCodeOfOrigin, requiresShipping (inventoryItemUpdate). activate: stock an item at a location (inventoryActivate). deactivate: remove an item from a location and its stock tracking there (inventoryDeactivate; needs confirm:"deactivate"). A SKU must match exactly one inventory item or the call is refused. Reads current quantities first; dryRun shows each row's before and after. input: {action: adjust|move|move_state|update_item|activate|deactivate, changes?: [{inventoryItemId?, sku?, locationId, delta}], items?: [{inventoryItemId?, sku?, quantity}], quantityName?: available, reason?: correction|cycle_count_available|damaged|movement_created|movement_updated|movement_received|movement_canceled|other|promotion|quality_control|received|reservation_created|reservation_deleted|reservation_updated|restock|safety_stock|shrinkage, referenceDocumentUri?, fromLocationId?, toLocationId?, locationId?, fromState?: available|damaged|quality_control|reserved|safety_stock, toState?: available|damaged|quality_control|reserved|safety_stock, inventoryItemId?, sku?, tracked?, cost?, countryCodeOfOrigin?, harmonizedSystemCode?, provinceCodeOfOrigin?, requiresShipping?, available?}

  • discount: Create, activate, deactivate, delete, add codes to, or lightly update a discount, code or automatic. Percentages are FRACTIONS from 0 to 1 (0.2 is 20% off). Money is a decimal string in the shop currency. create: kind amount_off, percentage, free_shipping or bxgy, method code or automatic, all customers only; refuses a code that already exists; needs an explicit startsAt; the dry run states the exact discount in words. activate and deactivate work on code and automatic discounts. delete needs confirm:"delete". add_codes adds up to 250 codes to a code discount and refuses codes that already exist. update changes only title, startsAt, endsAt and usageLimit. Use shopify_create_discount for a quick percentage code with customer segments. input: {action: create|activate|deactivate|delete|add_codes|update, id?, kind?: amount_off|percentage|free_shipping|bxgy, method?: code|automatic, title?, code?, startsAt?, endsAt?, percentage?, amount?, appliesOnEachItem?, appliesOncePerCustomer?, usageLimit?, minimumSubtotal?, minimumQuantity?, customerEligibility?, productIds?: [...], collectionIds?: [...], combinesWith?: {productDiscounts?, orderDiscounts?, shippingDiscounts?}, maximumShippingPrice?, buyQuantity?, buyProductIds?: [...], buyCollectionIds?: [...], getQuantity?, getProductIds?: [...], getCollectionIds?: [...], getPercentage?, usesPerOrderLimit?, codes?: [...]}

  • variants: Create, update and/or delete variants of one product (productVariantsBulkCreate / BulkUpdate / BulkDelete). Updates and deletes must name variants of this product. sku, tracked, cost, weight, requiresShipping, countryCodeOfOrigin and harmonizedSystemCode set the variant's inventory item. input: {productId, create?: [{price, compareAtPrice?, sku?, barcode?, optionValues: [{optionName, name}], inventoryPolicy?: DENY|CONTINUE, taxable?, tracked?, cost?, requiresShipping?, weight?: {value, unit: GRAMS|KILOGRAMS|OUNCES|POUNDS}, countryCodeOfOrigin?, harmonizedSystemCode?}], update?: [{id, price?, compareAtPrice?, sku?, barcode?, optionValues?: [{optionName, name}], inventoryPolicy?: DENY|CONTINUE, taxable?, tracked?, cost?, requiresShipping?, weight?: {value, unit: GRAMS|KILOGRAMS|OUNCES|POUNDS}, countryCodeOfOrigin?, harmonizedSystemCode?}], delete?: [...], strategy?: DEFAULT|REMOVE_STANDALONE_VARIANT|PRESERVE_STANDALONE_VARIANT}

  • options: Create, update and/or delete product options such as Size or Color (productOptionsCreate / productOptionUpdate / productOptionsDelete). createVariants:true also creates or removes the variants an option change implies; the default leaves variants as they are. input: {productId, create?: [{name, values: [...], position?}], update?: [{id, name?, position?, addValues?: [...], renameValues?: [{id, name}], deleteValueIds?: [...]}], delete?: [...], createVariants?}

  • delete: Permanently delete one product or customer by GID (productDelete / customerDelete). This cannot be undone: archive a product (shopify_update_product status ARCHIVED) when it may come back. Shopify refuses to delete a customer who has orders. input: {id}

  • create_customer: Create a customer (customerCreate) and add any addresses (customerAddressCreate; the first becomes the default). Marketing consent is out of scope: record it only from the customer's own opt-in. dryRun:true (the default) checks for an existing customer with the same email and previews the input. input: {firstName?, lastName?, email?, phone?, note?, tags?: [...], taxExempt?, locale?, addresses?: [{firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}]}

  • customer_address: Create, update, delete or set the default mailing address of a customer (customerAddressCreate / Update / Delete, customerUpdateDefaultAddress). addressId must belong to the customer. input: {customerId, action: create|update|delete|set_default, addressId?, address?: {firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}, setAsDefault?}

  • merge_customers: Merge two customer records into one (customerMerge). This cannot be undone. dryRun:true (the default) runs Shopify's customerMergePreview, which shows the resulting customer, the fields kept and anything blocking the merge. overrideFields chooses which customer's name, email, phone or default address to keep. input: {customerOneId, customerTwoId, overrideFields?: {customerIdOfFirstNameToKeep?, customerIdOfLastNameToKeep?, customerIdOfEmailToKeep?, customerIdOfPhoneNumberToKeep?, customerIdOfDefaultAddressToKeep?, note?, tags?: [...]}}

  • create_draft_order: Create a draft order (draftOrderCreate) from variants and/or custom line items, with an optional customer, addresses, discount and shipping line. No invoice is sent. dryRun:true (the default) runs draftOrderCalculate, which returns Shopify's real totals without creating anything. input: {lineItems: [{variantId?, title?, price?, quantity, sku?, taxable?, requiresShipping?}], customerId?, email?, phone?, note?, tags?: [...], poNumber?, taxExempt?, shippingAddress?: {firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}, billingAddress?: {firstName?, lastName?, company?, address1?, address2?, city?, provinceCode?, countryCode?, zip?, phone?}, useCustomerDefaultAddress?, appliedDiscount?: {value, valueType: FIXED_AMOUNT|PERCENTAGE, title?, description?}, discountCodes?: [...], shippingLine?: {title, price}, currencyCode?}

  • complete_draft_order: Complete a draft order and turn it into a real order (draftOrderComplete). Inventory is reserved and the order appears in the orders list. Without paymentGatewayId Shopify marks the order as paid. input: {id, paymentGatewayId?}

  • order_status: Cancel, close, reopen or mark an order as paid (orderCancel / orderClose / orderOpen / orderMarkAsPaid). cancel cannot be undone; it refunds the original payment only with refund:true and restocks only with restock:true. notifyCustomer defaults to false. The preview checks the action is allowed. input: {id, action: cancel|close|open|mark_paid, reason?: CUSTOMER|DECLINED|FRAUD|INVENTORY|STAFF|OTHER, refund?, restock?, notifyCustomer?, staffNote?}

  • refund: Refund line items and/or shipping on an order (refundCreate). The tool asks Shopify for the suggested refund (amounts, tax and the transactions to refund against) and refunds exactly that. dryRun:true (the default) returns the suggestion. To apply, pass dryRun:false with expectedAmount equal to the suggested total from the preview; any difference stops the write. notify defaults to false. input: {orderId, lineItems?: [{lineItemId, quantity, restockType?: NO_RESTOCK|CANCEL|RETURN, locationId?}], refundShipping?, shippingAmount?, note?, notify?, expectedAmount?}

Inputs: store (required), operation (required), input, dryRun, +1 more.

shopify_metafieldsA
Destructive

Set (metafieldsSet) and/or delete (metafieldsDelete) up to 25 metafields each, for any owner GID. Read them with shopify_get resource metafields. Defaults to dryRun:true.

Inputs: store (required), set, delete, dryRun.

shopify_redirectsA
Destructive

Create and/or delete up to 100 URL redirects each, with a per-redirect outcome (applied, rejected or unknown) and a store status. List them with shopify_search resource redirects. Requires write_online_store_navigation. Defaults to dryRun:true.

Inputs: store (required), create, delete, dryRun.

shopify_reportRun a Shopify ReportA
Read-onlyIdempotent

Run one read-only report across selected stores; each store returns its own result and completeness indicators. Reports:

  • portfolio_snapshot: Shop identity and product, order, customer and location counts. stores optional (all stores).

  • store_locations: Active, inactive, legacy, fulfillment, inventory and address status of locations. stores optional (all stores).

  • compare_inventory: Inventory, price, status and catalog details for exact SKUs. Needs skus (1-50).

  • compare_prices: Price and compare-at price for exact SKUs, with mismatches and missing variants. Needs skus (1-50).

  • get_product_everywhere: One exact SKU or handle across stores. Needs identifier and matchBy (sku or handle).

  • compare_catalog: Titles, status, vendor, type and inventory for exact product handles. Needs handles (1-50).

  • compare_collections: Titles, sort order, product counts, SEO and images for exact collection handles. Needs handles (1-50).

  • catalog_gap_report: Products missing or with different status across stores. first: products scanned per store (default 250).

  • catalog_health: Missing vendor, type, SEO, media, alt text, and active products without inventory. first (default 100).

  • duplicate_sku_report: SKUs repeated inside a store and shared across stores. first: variants scanned per store (default 250).

  • low_stock_report: Active variants at or below threshold (default 10), separating low, zero and negative.

  • recent_product_changes: Products updated in the last days (default 7). first (default 100).

  • list_unfulfilled_orders: Recent open unfulfilled orders. days (default 7), first (default 25).

  • fulfillment_sla_report: Open unfulfilled orders by age bucket and SLA breaches. lookbackDays (default 90), slaDays (default 2), first (default 100).

  • order_summary: Order values, discounts, shipping, tax, cancellations and statuses; currencies separate. days (default 30), first (default 100).

  • customer_growth: New customers in the current and previous period of days (default 30).

  • analytics: Run one ShopifyQL query on each store and return columns, rows and a chart hint. Needs query and read_reports.

Inputs: report (required), days, skus, first, +8 more.

shopify_run_actionRun a Shopify Admin ActionA
Destructive

Run any Shopify Admin API mutation on one to one hundred stores. Give a mutation name (a default document is built) or a full single-mutation document, plus variables shared by every store and/or variablesByStore (IDs differ per store). dryRun (the default) validates the document and variables against each store's API version and looks up every record ID in the variables and the document; nothing is changed. The preview says whether it is complete: targets chosen by a search, saved search, filter, or "all" flag, more than 250 IDs, or IDs that do not resolve make it incomplete, and then applying also needs acknowledgeIncompletePreview: true. dryRun false applies it; every ID is looked up again first, and IDs that do not resolve refuse the apply unless acknowledgeIncompletePreview is true. Destructive actions (delete, cancel, refund and similar) need confirm set to the mutation name. Mutations are never retried automatically. On a hosted server in per-user mode, Shopify limits this to what your own staff account may do.

Inputs: stores (required), dryRun, confirm, document, +4 more.

shopify_search_docs_chunksA
Read-onlyIdempotent

Search Shopify documentation and return source links. No store credentials are sent.

Inputs: prompt (required), api_name, max_num_results.

shopify_set_inventoryA
Destructive

Set available inventory at one location using compare-and-set protection: compareQuantity must equal the current available quantity. Read inventory first (shopify_get resource inventory). dryRun:true (the default) checks and previews without changing anything.

Inputs: store (required), quantity (required), locationId (required), compareQuantity (required), +4 more.

shopify_tagsA
Destructive

Add and/or remove tags on a product, order, customer or draft order by GID (tagsAdd/tagsRemove). Defaults to dryRun:true.

Inputs: store (required), ownerId (required), add, dryRun, +1 more.

shopify_update_collectionA
Destructive

Update collection fields, rules or image, and add products to a manual collection (addProductIds). dryRun:true (the default) returns the current collection and the change without applying it; dryRun:false applies it and returns before and after.

Inputs: id (required), store (required), image, title, +5 more.

shopify_update_customerA
Destructive

Update customer name, email, phone, note, tax exemption and tags (customerUpdate). dryRun:true (the default) returns the current customer and the change without applying it; dryRun:false applies it and returns before and after. Tags: addTags and removeTags change only the named tags; replaceTags replaces all tags. Email marketing consent is out of scope. Requires write_customers.

Inputs: id (required), store (required), note, email, +8 more.

shopify_update_orderA
Destructive

Update order note, email, phone, PO number, additional details (customAttributes), shipping address and tags (orderUpdate). dryRun:true (the default) returns the current order and the change without applying it; dryRun:false applies it and returns before and after. Tags: addTags and removeTags change only the named tags; replaceTags replaces all tags. Requires write_orders.

Inputs: id (required), store (required), note, email, +8 more.

shopify_update_pricesA
Destructive

Set price, compareAtPrice and/or unit cost for up to 250 SKUs on one store (store) or the same list on several stores in parallel (stores). Resolves each SKU to the variants whose SKU matches exactly (Shopify search is a prefix match) and groups writes by product. A SKU shared by several variants is skipped unless allowDuplicates:true. Duplicate SKU rows with conflicting values are rejected before any write; identical duplicates are collapsed. After a write, verifies each variant with a separate read-back query and reports per-item outcome (applied, applied_unverified, rejected, not_found, ambiguous, unknown, skipped, mismatch) and a store status (ok, unverified, partial, failed, unknown). Large results are trimmed, never dropped: status, counts and every item that did not apply are always returned. Defaults to dryRun:true.

Inputs: skus (required), store, dryRun, stores, +1 more.

shopify_update_productB
Destructive

Update product fields, variants, media and tags. dryRun:true (the default) returns the current product and the change without applying it; dryRun:false applies it and returns before and after. Tags: addTags and removeTags change only the named tags; replaceTags replaces all tags. A status of ARCHIVED or DRAFT takes the product off every sales channel.

Inputs: id (required), store (required), seo, title, +15 more.

shopify_upload_imageA
Destructive

Upload a local image file or an HTTPS image to Shopify Files, wait for processing, and return its CDN URL (check it later with shopify_get resource uploaded_image). Defaults to dryRun:true, which previews the upload without sending anything.

Inputs: store (required), alt, dryRun, filename, +2 more.

shopify_validate_graphql_codeblocksB
Read-onlyIdempotent

Validate Admin GraphQL operations against this store's API version without executing them.

Inputs: store (required), codeblocks (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 31 tools

    Disambiguation2/5

    Several tool pairs have unclear boundaries: shopify_manage bundles guided writes for webhooks, pages, articles, blogs, metaobjects, draft orders, files, inventory and discounts that also exist as dedicated tools (discount, inventory, fulfillment, create_draft_order, shopify_create_discount). Likewise shopify_run_action, shopify_graphql_mutation, shopify_graphql_query and shopify_graphql_query_many all overlap as generic escape hatches, and shopify_update_product vs variants vs options vs shopify_tags vs shopify_metafields require careful reading to pick correctly.

    Naming Consistency2/5

    Naming mixes a shopify_ prefix for many tools (shopify_create_product, shopify_get, shopify_search, shopify_report) with bare noun or verb names (delete, variants, options, refund, inventory, fulfillment, discount, customer_address, create_draft_order, order_status). The verb_noun convention is absent in the bare-named tools, so an agent cannot predict a tool's name from its function.

    Tool Count2/5

    31 tools exceeds a well-scoped surface, and part of that count is redundancy: four separate GraphQL escape hatches (schema, query, query_many, mutation, validate_codeblocks, run_action, describe_action, find_actions) plus a mega-tool shopify_manage duplicate capabilities already exposed by dedicated tools. The Shopify admin domain is broad, but the set could be meaningfully consolidated.

    Completeness4/5

    Coverage is unusually broad: products, variants, options, collections, orders, refunds, customers and addresses, inventory, discounts, files, pages, articles, blogs, metaobjects, metafields, webhooks and redirects all have lifecycle operations, and shopify_run_action fills remaining gaps. Minor omissions remain (e.g. collection delete, theme file editing, gift cards), though most are reachable through the generic mutation tools.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Shopify store data via the GraphQL Admin API to manage products, customers, orders, and collections. Supports multi-store configurations and provides comprehensive management tools for e-commerce administration in both local and remote environments.
      12 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables management of Shopify store via GraphQL, including products, orders, inventory, and discounts with security features like preview mode and write protection.
      -