shopify-multi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPIFY_STORES | No | Comma-separated store definitions in the form 'name=domain', for example 'au=acme-au.myshopify.com,nz=acme-nz.myshopify.com'. These add to the saved stores for that run. | |
| XDG_CONFIG_HOME | No | Base configuration directory used when SHOPIFY_MULTI_MCP_HOME is not set. | |
| SHOPIFY_CLI_VERSION | No | Pin an exact Shopify CLI version instead of the newest. | |
| SHOPIFY_MULTI_MCP_HOME | No | Directory used for connected-store configuration (stores.json and related files). | |
| OPT_OUT_INSTRUMENTATION | No | Shopify's own telemetry opt-out for Dev MCP, passed through unchanged (for example 'true'). | |
| SHOPIFY_DEV_MCP_VERSION | No | Pin an exact Shopify Dev MCP version instead of the newest. | |
| SHOPIFY_MULTI_MCP_UPDATES | No | Set to 'session' to resolve versions once per server start and keep them for the session. | |
| SHOPIFY_MULTI_MCP_HIDE_TOOLS | No | Comma-separated Dev MCP tools to leave out, for example 'feedback'. | |
| SHOPIFY_MULTI_MCP_UPDATE_MINUTES | No | Minutes between update checks while the server is running. | 15 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storesA | List every store this server can work on: its name (the value to pass as "store"), myshopify.com domain, label, read-only flag, sign-in status, granted scopes and token expiry, plus the Shopify CLI and Dev MCP versions in use. Call this first when you are unsure which stores exist or why a call failed. |
| connect_storeA | Add a store, or sign in to one again when its session expired. Opens Shopify's own sign-in page in the user's browser (Shopify CLI "store auth"); the user must approve there, so tell them to look for the browser window. Returns within about 20 seconds; if approval is still pending, call it again with the same name to wait for the result. |
| get_shopB | Name, domains, contact email, currency, timezone and plan of one store. |
| search_productsA | Search or list products in one store. Returns id, title, handle, status, vendor, type, tags, total inventory and price range. "query" uses Shopify search syntax, for example |
| list_ordersA | List orders in one store, newest first. "query" uses Shopify order search syntax, for example |
| graphql_queryA | Run a read-only Shopify Admin GraphQL query on one store; mutations are refused here. Use it for anything the curated tools do not cover. Before writing an unfamiliar query, look the fields up with learn_shopify_api (api "admin") and check it with validate (api "admin"). Select pageInfo { hasNextPage endCursor } on connections. Uses the latest stable Admin API version unless api_version is set. |
| graphql_mutationA | Run a Shopify Admin GraphQL mutation that changes data in one store. Confirm the target store and the change with the user before calling. Validate the document with validate (api "admin") first, look ids up in the same store (ids from another store will not resolve), and check the userErrors field of the result. Refused for read-only stores. |
| graphql_query_all_storesA | Run the same read-only Admin GraphQL query on several stores at once and get the results side by side, each labelled with its store. For common comparisons (sales, unfulfilled orders, low stock, catalogue gaps) store_report is quicker and already combines the answers. |
| store_reportA | Ask every store (or the ones listed) at once and get one combined, store-labelled answer. Reports:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| morning-check | Overview, unfulfilled orders by age and low stock for every connected store. |
| sales | Orders, sales and average order value per store for a period. |
| unfulfilled-orders | Open orders waiting to ship, grouped by age, in every store. |
| low-stock | Variants at or below a stock threshold, with stock available in the other stores. |
| compare-product | Price, status and stock of one product in every store. |
| catalogue-check | Products missing from some stores, status mismatches, and listings with no image, alt text or description. |
| connect-store | Sign in to a Shopify store through Shopify's own approval page. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools are clearly distinct (list_stores vs get_shop vs connect_store; single-store search_products vs multi-store find_product in store_report). The main overlap is graphql_query vs graphql_query_all_stores vs store_report, all of which fetch read data across stores; the descriptions distinguish them (one store, many stores, and pre-built comparison reports), but the boundary is soft enough to occasionally confuse selection.
Names are consistently snake_case with a verb_noun pattern (list_stores, connect_store, search_products, graphql_query, graphql_mutation). Minor deviations: 'store_report' is a noun-style aggregator rather than a verb, and the terminology mixes 'store' with 'shop' (get_shop) for the same entity.
Nine tools is well-scoped for a multi-store Shopify admin server, with curated helpers plus generic GraphQL escape hatches. Each tool earns its place without excess.
The surface covers auth, store discovery, product/order reads, single- and multi-store queries, and writes via graphql_mutation, so core workflows are complete. Gaps are minor: no first-class create/update/delete for products or orders (deferred to GraphQL), which is a reasonable design but leaves some lifecycle operations indirect.