Shopify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Shopify store domain (command-line argument) | |
| accessToken | No | Shopify Admin API access token (command-line argument) | |
| MYSHOPIFY_DOMAIN | No | Shopify store domain (e.g., your-store.myshopify.com) | |
| SHOPIFY_ACCESS_TOKEN | No | Shopify Admin API access token |
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-productsD | – |
| get-product-by-idD | – |
| get-customersD | – |
| get-ordersD | – |
| get-order-by-idD | – |
| update-orderD | – |
| get-customer-ordersD | – |
| update-customerD | – |
| create-productD | – |
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 9 tools
Each tool has a clearly distinct purpose targeting specific resources and actions. For example, get-products retrieves a list while get-product-by-id fetches a single item, and create-product vs. update-order handle different operations on different entities. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern with hyphens, such as create-product, get-orders, and update-customer. The naming is uniform throughout, using clear verbs (create, get, update) paired with specific nouns (product, customer, order), making it predictable and readable.
With 9 tools, the server is well-scoped for a Shopify integration, covering core e-commerce operations. Each tool serves a distinct function in managing products, customers, and orders, and the count is neither too sparse nor overwhelming for the domain.
The tool set provides good coverage for CRUD operations on products, customers, and orders, including create, get, and update actions. However, there are minor gaps such as no delete operations (e.g., delete-product) and missing tools for other Shopify resources like inventory or discounts, which agents might need to work around.