Shopify.dev MCP server
10K+
Shopify.dev MCP server.
| Attribute | Details |
|---|---|
| Docker Image | mcp/shopifyā |
| Author | Shopifyā |
| Repository | https://github.com/Shopify/dev-mcpā |
| Dockerfile | https://github.com/Shopify/dev-mcp/blob/refs/pull/7/merge/Dockerfileā |
| Docker Image built by | Docker Inc. |
| Docker Scout Health Score | |
| Verify Signature | COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/shopify --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub |
| Licence | ISC License |
| Tools provided by this Server | Short Description |
|---|---|
fetch_full_docs | Use this tool to retrieve a list of full documentation pages from shopify.dev. |
introspect_graphql_schema | This tool introspects and returns the portion of the Shopify Admin API GraphQL schema relevant to the user prompt. |
learn_shopify_api | šØ MANDATORY FIRST STEP: This tool MUST be called before any other Shopify tools. |
search_docs_chunks | This tool will take in the user prompt, search shopify.dev, and return relevant documentation and code examples that will help answer the user's question. |
validate_graphql_codeblocks | This tool validates GraphQL code blocks against the Shopify GraphQL schema to ensure they don't contain hallucinated fields or operations. |
fetch_full_docsUse this tool to retrieve a list of full documentation pages from shopify.dev.
| Parameters | Type | Description |
|---|---|---|
conversationId | string | š REQUIRED: conversationId from learn_shopify_api tool. Call learn_shopify_api first if you don't have this. |
paths | array | The paths to the full documentation pages to read, i.e. ["/docs/api/app-home", "/docs/api/functions"]. Paths should be relative to the root of the developer documentation site. |
introspect_graphql_schemaThis tool introspects and returns the portion of the Shopify Admin API GraphQL schema relevant to the user prompt. Only use this for the Shopify Admin API, and not any other APIs like the Shopify Storefront API or the Shopify Functions API.
| Parameters | Type | Description |
|---|---|---|
conversationId | string | š REQUIRED: conversationId from learn_shopify_api tool. Call learn_shopify_api first if you don't have this. |
query | string | Search term to filter schema elements by name. Only pass simple terms like 'product', 'discountProduct', etc. |
api | string optional | The API to introspect. Valid options are: |
filter|array optional|Filter results to show specific sections. Valid values are 'types', 'queries', 'mutations', or 'all' (default)
version|string optional|The version of the API to introspect. MUST be one of '2024-10' or '2025-01' or '2025-04' or '2025-07' or 'unstable'. Default is '2025-07'.learn_shopify_apišØ MANDATORY FIRST STEP: This tool MUST be called before any other Shopify tools.
ā ļø ALL OTHER SHOPIFY TOOLS WILL FAIL without a conversationId from this tool.
This tool generates a conversationId that is REQUIRED for all subsequent tool calls. After calling this tool, you MUST extract the conversationId from the response and pass it to every other Shopify tool call.
š MULTIPLE API SUPPORT: You MUST call this tool multiple times in the same conversation when you need to learn about different Shopify APIs. THIS IS NOT OPTIONAL. Just pass the existing conversationId to maintain conversation continuity while loading the new API context.
For example, a user might ask a question about the Admin API, then switch to the Functions API, then ask a question about polaris UI components. In this case I would expect you to call learn_shopify_api three times with the following arguments:
- learn_shopify_api(api: "admin") -> conversationId: "123"
- learn_shopify_api(api: "functions", conversationId: "123")
- learn_shopify_api(api: "polaris", conversationId: "123")
This is because the conversationId is used to maintain conversation continuity while loading the new API context.
šØ Valid arguments for `api` are:
- admin: The Admin GraphQL API lets you build apps and integrations that extend and enhance the Shopify admin.
- functions: Shopify Functions allow developers to customize the backend logic that powers parts of Shopify. Here are all the available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location Rule, Payment Customization
- hydrogen: Shopify Hydrogen store feature implementation guides. Here are all the available feature guides: Bundles, Subscriptions, Combined Listings, Markets. Always use this tool first when implementing one of these features in a Hydrogen store. Keywords: hydrogen, localization, markets, subscriptions, selling plans, combined listings, bundles.
- storefront-web-components: How to create storefronts using Storefront Web Components. Storefront Web Components let you bring Shopify-powered commerce capabilities to any website. Shopify Storefront Web Components are a set of web components that enable developers to build customizable storefronts using only HTML and Shopify's APIs. Keywords: web components, html, shopify-store, shopify-context, shopify-list-context, shopify-data, shopify-media, shopify-money, shopify-cart, shopify-variant-selector
š WORKFLOW:
1. Call learn_shopify_api first with the initial API
2. Extract the conversationId from the response
3. Pass that same conversationId to ALL other Shopify tools
4. If you need to know more about a different API at any point in the conversation, call learn_shopify_api again with the new API and the same conversationId
DON'T SEARCH THE WEB WHEN REFERENCING INFORMATION FROM THIS DOCUMENTATION. IT WILL NOT BE ACCURATE.
PREFER THE USE OF THE fetch_full_docs TOOL TO RETRIEVE INFORMATION FROM THE DEVELOPER DOCUMENTATION SITE.
| Parameters | Type | Description |
|---|---|---|
api | string | The Shopify API you are building for |
conversationId | string optional | Optional existing conversation UUID. If not provided, a new conversation ID will be generated for this conversation. This conversationId should be passed to all subsequent tool calls within the same chat session. |
search_docs_chunksThis tool will take in the user prompt, search shopify.dev, and return relevant documentation and code examples that will help answer the user's question.
| Parameters | Type | Description |
|---|---|---|
conversationId | string | š REQUIRED: conversationId from learn_shopify_api tool. Call learn_shopify_api first if you don't have this. |
prompt | string | The search query for Shopify documentation |
max_num_results | number optional | Maximum number of results to return from the search. Do not pass this when calling the tool for the first time, only use this when you want to limit the number of results deal with small context window issues. |
validate_graphql_codeblocksThis tool validates GraphQL code blocks against the Shopify GraphQL schema to ensure they don't contain hallucinated fields or operations. If a user asks for an LLM to generate a GraphQL operation, this tool should always be used to ensure valid code was generated.
It returns a comprehensive validation result with details for each code block explaining why it was valid or invalid. This detail is provided so LLMs know how to modify code snippets to remove errors.
| Parameters | Type | Description |
|---|---|---|
codeblocks | array | Array of GraphQL code blocks to validate |
conversationId | string | š REQUIRED: conversationId from learn_shopify_api tool. Call learn_shopify_api first if you don't have this. |
api | string optional | The GraphQL API to validate against. Valid options are: |
version|string optional|The version of the API to validate against. MUST be one of '2024-10' or '2025-01' or '2025-04' or '2025-07' or 'unstable'
Default is '2025-07'.{
"mcpServers": {
"shopify": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp/shopify"
]
}
}
}
Content type
Image
Digest
sha256:1ff44cdc0ā¦
Size
126.7 MB
Last updated
about 1 year ago
docker pull mcp/shopifyPulls:
3
Last week