MCP Shopify Admin Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPIFY_ACCESS_TOKEN | Yes | Your Shopify Admin API access token | |
| SHOPIFY_STORE_DOMAIN | Yes | Your Shopify store domain (e.g., your-store.myshopify.com) |
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 |
|---|---|
| store_listA | List all configured Shopify stores. Use this to see available stores before performing operations. Each store has a name, environment (production/staging/development), and default status. |
| operation_listA | List all pending operations that are waiting for preview or execution. Operations expire after 30 minutes if not executed. |
| operation_statusA | Get detailed status of a specific operation including its current state, preview data, and result. |
| operation_cancelA | Cancel a pending operation that has not yet been executed. This is useful if you want to discard a planned operation. |
| product_listA | List products from a Shopify store with optional filtering and pagination. |
| product_getA | Get detailed information about a specific product including variants, images, and inventory. |
| product_searchA | Search for products using Shopify's search syntax. |
| product_create_planA | Plan a new product creation. This creates a staged operation that must be previewed and then executed. No changes are made until execution. |
| product_create_previewA | Preview a planned product creation. Shows exactly what will be created. Must be called before execution. |
| product_create_executeA | Execute a previewed product creation. This actually creates the product. Requires prior preview. Production stores require confirm_production: true. |
| product_update_planA | Plan a product update. Creates a staged operation that must be previewed and executed. Only provided fields will be updated. |
| product_update_previewA | Preview a planned product update. Shows the diff between current and new values. |
| product_update_executeA | Execute a previewed product update. Requires prior preview. Production stores require confirm_production: true. |
| product_bulk_update_planB | Plan a bulk update of multiple products. Each product can have different updates. |
| product_bulk_update_previewA | Preview all changes in a bulk product update operation. |
| product_bulk_update_executeA | Execute a previewed bulk product update. Production stores require confirm_production: true. |
| product_tags_add_planA | Plan an ADDITIVE tag operation across products. Uses Shopify's tagsAdd mutation, which appends tags without touching existing ones — safe to run concurrently and immune to the stale-snapshot tag loss that productUpdate causes. Use this instead of product_update whenever you only need to add tags. Supply either |
| product_tags_add_previewA | Preview an additive tag operation. Shows, per product, which tags are genuinely new versus already present. |
| product_tags_add_executeA | Execute a previewed additive tag operation via Shopify's tagsAdd mutation. Existing tags are never removed. Production stores require confirm_production: true. |
| product_tags_remove_planA | Plan a SUBTRACTIVE tag operation using Shopify's tagsRemove mutation. Removes only the named tags and leaves every other tag untouched. |
| product_tags_remove_previewA | Preview a subtractive tag operation — shows which named tags are actually present per product. |
| product_tags_remove_executeA | Execute a previewed subtractive tag operation via tagsRemove. Production stores require confirm_production: true. |
| collection_listA | List collections in a store. Shows whether each collection is MANUAL (hand-picked products) or AUTOMATED (rule-based), plus its rules and product count. Only AUTOMATED collections propagate their membership to external product feeds such as the Meta catalog. |
| collection_getA | Get one collection by numeric ID, full GID, or handle. Reports MANUAL vs AUTOMATED and the rule set. |
| collection_update_planA | Plan an update to a collection. The main use is converting a MANUAL collection into an AUTOMATED one by supplying a rule_set (e.g. TAG EQUALS 'or-cocktail-dresses'), which makes its membership visible to external product feeds like the Meta catalog. Staged: must be previewed then executed. |
| collection_update_previewA | Preview a planned collection update, showing current vs new state. |
| collection_update_executeA | Execute a previewed collection update. Production stores require confirm_production: true. Note: Shopify may reject converting an existing manual collection to automated; if so, create a new automated collection with collection_create instead. |
| collection_create_planB | Plan creation of a new collection, optionally AUTOMATED via a rule_set. Use this when Shopify refuses to convert an existing manual collection: create an automated twin, then point downstream systems at it. |
| collection_create_previewB | Preview a planned collection creation. |
| collection_create_executeA | Execute a previewed collection creation. Production stores require confirm_production: true. |
| publication_listA | List the store's publications (sales channels) — Online Store, Facebook & Instagram, Point of Sale, etc. You need a publication ID before you can publish a product to a channel. |
| product_publications_getA | Show which sales channels a product is published to. Useful for diagnosing products that exist in a collection but never appear on the storefront or in an external feed. |
| product_publish_planA | Plan publishing one or more products to one or more sales channels. Use publication_list to get channel IDs. Staged: must be previewed then executed. |
| product_publish_previewA | Preview which products will change publication state, and on which channels. |
| product_publish_executeA | Execute a previewed publish. Publishing is additive — it never unpublishes a product from a channel it is already on. Production stores require confirm_production: true. |
| order_listB | List orders from a Shopify store with optional filtering by status and pagination. |
| order_getA | Get detailed information about a specific order including line items, fulfillments, and customer info. |
| order_fulfill_planA | Plan an order fulfillment. This creates a staged operation that must be previewed and executed. |
| order_fulfill_previewA | Preview a planned order fulfillment. Shows what will be shipped. |
| order_fulfill_executeA | Execute a previewed order fulfillment. This marks items as shipped. Production stores require confirm_production: true. |
| order_cancel_planA | Plan an order cancellation. This creates a staged operation that must be previewed and executed. |
| order_cancel_previewA | Preview a planned order cancellation. Shows what will happen. |
| order_cancel_executeA | Execute a previewed order cancellation. This actually cancels the order. Production stores require confirm_production: true. |
| customer_listA | List customers from a Shopify store with optional search and pagination. |
| customer_getA | Get detailed information about a specific customer including their address and recent orders. |
| inventory_levelsA | Get inventory levels for products at specific locations. Can filter by location, product, or SKU. |
| inventory_adjust_planA | Plan an inventory adjustment. Creates a staged operation that must be previewed and executed. |
| inventory_adjust_previewA | Preview a planned inventory adjustment. Shows the before and after quantities. |
| inventory_adjust_executeA | Execute a previewed inventory adjustment. This actually changes the inventory. Production stores require confirm_production: true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxiomus/mcp-shopify-admin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server