Shopify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSHOPIFY_DOMAIN | No | Your Shopify store domain, e.g. your-store.myshopify.com | |
| SHOPIFY_CLIENT_ID | No | Your Shopify app Client ID from the Dev Dashboard app's API credentials. Used with client credentials authentication (Dev Dashboard apps, January 2026+). | |
| SHOPIFY_API_VERSION | No | The Shopify API version to use. Can also be set via the --apiVersion command-line option. | 2026-10 |
| SHOPIFY_ACCESS_TOKEN | No | Static Shopify access token (shpat_...) for legacy custom apps. | |
| SHOPIFY_CLIENT_SECRET | No | Your Shopify app Client Secret from the Dev Dashboard app's API credentials. The server exchanges the client ID and secret for an access token and refreshes it before it expires. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-productsB | Get all products or search by title. Supports field selection via 'fields' and 'countOnly' to get just the count. |
| get-product-by-idB | Get a specific product by ID. Supports field selection via 'fields' to reduce response size. |
| create-productA | Create a new product. When using productOptions, Shopify registers all option values but only creates one default variant (first value of each option, price $0). Use manage-product-variants with strategy=REMOVE_STANDALONE_VARIANT afterward to create all real variants with prices. |
| update-productC | Update an existing product's fields (title, description, status, tags, etc.) |
| delete-productC | Delete a product |
| manage-product-variantsB | Create or update product variants. Omit variant id to create new, include id to update existing. |
| delete-product-variantsC | Delete one or more variants from a product |
| manage-product-optionsA | Create, update, or delete product options (e.g. Size, Color). Use action='create' to add options, 'update' to rename or add/remove values, 'delete' to remove options. |
| add-product-mediaA | Attach images to an existing product by public URL. Shopify processes media asynchronously: new items usually start as UPLOADED or PROCESSING. Use get-product-media to confirm they reach READY. |
| get-product-mediaA | List a product's media with processing status (UPLOADED / PROCESSING / READY / FAILED), alt text, and image URL. Use after add-product-media to confirm processing finished. |
| get-ordersB | Get orders with optional filtering by status. Supports field selection via 'fields' and 'countOnly' to get just the count. |
| get-order-by-idC | Get a specific order by ID. Supports field selection via 'fields' to reduce response size. |
| update-orderC | Update an existing order with new information |
| create-draft-orderB | Create a draft order for phone/chat sales, invoicing, or wholesale. Supports custom line items, discounts, and customer association. |
| complete-draft-orderC | Complete a draft order, converting it into a real order. Optionally specify a payment gateway. |
| order-cancelB | Cancel an order with options for refunding, restocking inventory, and customer notification. Cancellation is irreversible. |
| order-close-openA | Close or reopen an order. Closing marks all items fulfilled and finances complete. Opening reopens a closed order. |
| order-mark-as-paidA | Mark an order as paid. Useful for manual/offline payments (cash, bank deposit, etc.). |
| create-fulfillmentA | Create a fulfillment (mark items as shipped) with optional tracking info. IMPORTANT: Call get-fulfillment-orders first to obtain the fulfillmentOrderId and line item GIDs. |
| refund-createB | Create a full or partial refund for an order with optional restocking and shipping refund. |
| get-customersB | Get customers or search by name/email. Supports field selection via 'fields' and 'countOnly' to get just the count. |
| get-customer-by-idA | Get a single customer by ID. Supports field selection via 'fields' to reduce response size. |
| get-customer-ordersC | Get orders for a specific customer. Supports field selection via 'fields' to reduce response size. |
| create-customerC | Create a new customer |
| update-customerC | Update a customer's information |
| delete-customerC | Delete a customer |
| customer-mergeC | Merge two customer records into one. Optionally override which fields to keep from which customer. |
| manage-customer-addressC | Create, update, or delete a customer's mailing address. Can optionally set as default. |
| get-metafieldsB | Get metafields for any Shopify resource (products, orders, customers, variants, collections, etc.). Supports 'keys' filter to fetch only specific metafields by namespace.key. |
| set-metafieldsA | Set metafields on any Shopify resource (products, orders, customers, variants, collections, etc.). Creates or updates up to 25 metafields atomically. |
| delete-metafieldsC | Delete metafields from any Shopify resource by specifying owner ID, namespace, and key. |
| manage-tagsB | Add or remove tags on any taggable resource (orders, products, customers, draft orders, articles). |
| manage-tags-bulkA | Bulk add or remove tags on up to 100 resources in a single call. IMPORTANT: Prefer this over calling manage-tags repeatedly — it runs all mutations in parallel and returns per-resource results. |
| inventory-set-quantitiesA | Set absolute inventory quantities for items at specific locations. Use for inventory corrections, cycle counts, etc. Pass changeFromQuantity per item to only apply the change if the current quantity still matches. Returns the idempotencyKey used, so a failed call can be retried with the same key, plus userErrors. |
| update-inventory-itemA | Set an inventory item's unit cost and/or whether its inventory is tracked. Provide at least one of cost or tracked. Read the cost back with get-inventory-items. |
| get-shop-infoA | Get shop configuration including name, plan, currencies, features, payment settings, tax config, and contact info |
| get-metafield-definitionsA | Discover custom metafield definitions for any resource type (PRODUCT, ORDER, CUSTOMER, etc.). Returns namespace, key, name, type, and validations. |
| get-locationsA | Get all inventory/fulfillment locations with addresses, capabilities, and active status |
| get-marketsB | Get all markets with their regions, currencies, status, and web presence configuration |
| get-collectionsA | Query collections (manual & smart) with optional filtering. Supports field selection via 'fields' to reduce response size. Returns title, handle, products count, sort order, and rules for smart collections. |
| get-order-transactionsA | Get all payment transactions for an order including authorizations, captures, refunds, and voids with gateway, status, and amounts |
| get-fulfillment-ordersA | Get fulfillment orders for an order including status, assigned location, delivery method, holds, and line items |
| get-order-refund-detailsB | Get detailed refund info for an order including refunded items, amounts, restock status, and associated transactions |
| get-collection-by-idA | Get a single collection with full details including products (paginated), rules for smart collections, SEO, and image. Supports field selection via 'fields' to reduce response size. |
| get-inventory-levelsB | Get inventory quantities per location for an inventory item (available, on_hand, committed, reserved, incoming, damaged, etc.) |
| get-inventory-itemsB | Get inventory item details for all variants of a product including SKU, cost, tracked status, country of origin, and HS codes |
| get-price-listsC | Get all price lists with their currency, fixed/relative adjustments, and associated catalog context |
| get-product-variants-detailedA | Get all variant fields for a product: pricing, inventory, barcode, weight, tax code, selected options, metafields, and image. Supports field selection via 'fields' to reduce response size. |
| get-publicationsA | List the store's sales channels (publications), e.g. Online Store and Point of Sale, with their IDs. Use the names or IDs with publish-product / unpublish-product. |
| get-product-publicationsB | Show whether a product is published on each sales channel (published true/false, with publishDate when published or scheduled). |
| publish-productA | Publish a product to one or more sales channels, by publicationIds or exact publicationNames (see get-publications). Returns the product's state on every channel afterwards, plus userErrors. |
| unpublish-productA | Unpublish a product from one or more sales channels, by publicationIds or exact publicationNames (see get-publications). Returns the product's state on every channel afterwards, plus userErrors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 52 tools
Most tools target a distinct resource and action, such as get-products vs get-product-by-id, get-orders vs get-customer-orders, and add-product-media vs get-product-media. Some boundaries are less crisp, especially get-inventory-items vs get-product-variants-detailed and manage-tags vs manage-tags-bulk, but descriptions generally clarify when to use each.
The set is consistently kebab-case, but verb placement and prefixes vary: get-products, create-product, manage-product-variants, order-cancel, refund-create, inventory-set-quantities, and customer-merge. It remains readable, but the mix of get/create/update/delete with manage-* and resource-prefixed action names is not fully predictable.
At 52 tools, the server is very heavy even for Shopify's broad admin surface. Many tools are granular GET endpoints and several CRUD pairs could be consolidated, so the count feels excessive despite covering many real operations.
Core product, order, customer, inventory, fulfillment, refund, metafield, publication, and tag workflows are covered. However, notable gaps remain: collections are read-only, discounts are absent, price lists and markets are read-only, and media cannot be deleted.