Shopify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSHOPIFY_DOMAIN | Yes | Your Shopify store domain (e.g., your-store.myshopify.com) | |
| SHOPIFY_ACCESS_TOKEN | Yes | Your Shopify Admin API access token obtained from creating a custom app in your Shopify store |
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
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 15 tools
Each tool targets a distinct Shopify resource (articles, blogs, collections, pages, products, or search) with clear naming, leaving no ambiguity for an agent.
All tools follow a verb-noun pattern with hyphens (e.g., create-article, get-product-by-id). Minor inconsistency: some resources have both singular and plural get endpoints (e.g., get-article-by-id and get-articles) while others only have plural (get-collections, get-pages), but overall pattern is clear.
With 15 tools, the set is at the upper end of well-scoped but still reasonable for a Shopify server covering multiple resource types. No redundant tools.
The tool set is missing critical CRUD operations: only articles have create and update; no create for blogs, collections, pages, or products; no delete endpoints at all; and singular get is missing for collections and pages. This leaves significant gaps for common workflows.