MCP App Store
by KeenEthics
Shopify icon

Shopify MCP Server for Claude and ChatGPT

By Shopify

Overview

Shopify for ChatGPT makes starting, running, and growing an online store as easy as having a conversation. Turn a small business idea into an ecommerce website with Shopify’s AI store builder: describe what you sell, create your store, add products, and sell online. Already have a Shopify store? Connect it to manage inventory across locations, create discount codes, review orders and customer details, and pull analytics on your store’s performance. Shopify supports selling online, in person, B2B, on marketplaces, and selling internationally. Whether you run a print on demand business, sell digital products, operate an online boutique, dropship, or serve wholesale buyers, Shopify gives you the foundation to build, sell, and grow.

How to connect

  1. Claude: Open the Shopify listing in the Claude connectors directory and choose Connect. Claude listing Shopify exposes 25 tools here.
  2. ChatGPT: Open the Shopify listing in the ChatGPT app directory and choose Connect. ChatGPT listing Shopify exposes 65 tools here.

Tools

add-to-collection

ChatGPT
Add one or more products to a collection in the connected Shopify store. Use this when the user wants to organize products into a collection. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

attach-digital-file

ChatGPT
Mint a signed upload URL for one file on a Digital Products variant. Called by the upload widget, not by the model: it hands back a write credential and does not attach anything on its own. Attachment is recorded afterwards by finalize-digital-file-attachment.

attach-digital-product-media

ChatGPT
Mint a staged upload target for one media image on a digital product. Called by the media image upload widget, not by the model: it hands back a write credential and attaches nothing on its own. The image is attached afterwards by finalize-digital-product-media.

bulk-update-product-status

ChatGPT
Update the status of multiple products at once. Accepts a list of product IDs or a collectionId and a target status (ACTIVE, DRAFT, or ARCHIVED). Each product is updated individually so partial failures are possible. When using collectionId, only the first 50 products in the collection will be updated. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

claim-storefront-preview

ChatGPT
Signal that the user clicked a storefront preview's signup link. Revokes the current shop token (if any) so the next tool call prompts a fresh OAuth for the newly claimed store. Called only by the get-new-store-previews tool's widget — never invoke directly from the model.

create-collection

ChatGPT
Create a new collection in the connected Shopify store and publish it to the Online Store. Use this when the user wants to organize products into a new group. COLLECTION TYPES: - Manual collection: pass productIds to add specific products. - Smart collection: pass ruleSet with conditions to auto-populate products. - productIds and ruleSet are mutually exclusive — provide one or neither. SMART COLLECTION RULES: - Common rule columns: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE. - Common relations: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN. - appliedDisjunctively: true means products matching ANY rule are included (OR logic). - appliedDisjunctively: false means products must match ALL rules (AND logic). IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you have a local file, generated image, or external URL: call the upload-image tool FIRST to get a permanent Shopify CDN URL, then pass that URL here. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real collections. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

create-digital-product

ChatGPT
Create a draft product through Shopify Digital Products. The result includes the product and first variant identifiers used to attach and deliver the digital file. To set the price and the buyer-facing description, call update-product with productId as its 'id' and variantId in 'variants' — prices are in the shop's own currency, so ask the merchant for the amount rather than guessing one. Do not rename the product through update-product: Digital Products keeps its own copy of the title. This tool does not publish the draft.

create-discount

ChatGPT
Create a percentage-based discount code for the connected Shopify store. Use this when the merchant wants to set up a new discount code with a specific percentage off. Supports scoping to a specific collection, and optional minimum purchase or quantity requirements. The discount will be immediately active unless a future startsAt date is provided, in which case it will be scheduled. Always confirm with the merchant whether they want the discount active right away or scheduled for a specific date before creating it. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

create-product

ChatGPT
Create a new product in the connected Shopify store. Use this when the user wants to add a product with a title, description, variants, images, or other product details. VARIANTS & OPTIONS: - When providing variants, you MUST also provide the options field as a string array of option names. - Example: for a single default variant use options: ['Title'], for Size/Color variants use options: ['Size', 'Color']. - The options field must be an array of strings (e.g. ['Size', 'Color']), NOT an array of objects. - Each variant's optionValues must reference option names declared in the options array. INVENTORY TRACKING: - To enable inventory tracking on variants, set inventoryItem: { tracked: true } on each variant. - If omitted, inventory defaults to untracked and set-inventory will not work as expected. IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you have a local file, generated image, or external URL: call the upload-image tool FIRST to get a permanent Shopify CDN URL, then pass that URL here. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real products. - The first image provided becomes the product's featured image. COLLECTION: - Optionally pass collectionId to add the product to a collection after creation. - To add to multiple collections, use add-to-collection afterward. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

create-product-interactive

ChatGPT
Open an interactive product creation app for the connected Shopify store. Use this when the user wants to add a product and would benefit from reviewing or editing the product details before creation. Pre-fill as much product information as the user has provided. Do NOT invent values for the title. If the user has not told you what they're trying to sell and has not added an image of their product, ask them what the product is or ask for an image before calling this tool. If the user has not provided an exact product title or description, generate a sensible merchant-ready draft title and description from the available product details before opening the app, then let the user review or adjust them. AFTER THE APP SAVES A PRODUCT: It tells you it saved and gives you the product GID. To change that saved product's name, description, or first-variant price in the app, call the interactive editing app with that product GID and the full rendered product state the product should have now. Calling this creation app again starts a new product draft. That editing call only re-seeds the app, so do not report a change as saved until the merchant saves it, and do not write those three fields with update-product while the app holds the product — the merchant's next Save would overwrite you. Every other field, including status, images, and the product's other variants, is still yours to update directly. IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you have a local file, generated image, or external URL: call the upload-image tool FIRST to get a permanent Shopify CDN URL, then pass that URL here.

create-sample-product

ChatGPT
Create a sample product selected in the find-sample-product widget.

create_store

ChatGPT
Create a new Shopify store the user can start building right away, without signing in or creating an account. Returns a link to preview it, and the store's domain, which is its ID for tool calls. It's where someone with no Shopify store connected starts when they want to sell something or start a business. WHEN TO USE: - The user says they want to sell something, e.g. "I want to sell handmade soy candles", and has no Shopify store connected. - The user wants to start a business, open a shop or start selling online, and has no Shopify store connected. - The user asks you to create, make or build a store, and has no Shopify store connected. - The user asks to see store designs, or what their store could look like, and has no Shopify store connected. A new store's preview link shows its design. - The user wants to try building a store before signing up. A mockup or a described design is not a store; a store's design is its preview link. WHEN NOT TO USE: - A store is already connected and the user wants to work on it. Call graphql_query and graphql_mutation without store. - A store was already created in this conversation. Keep using its domain; a new one starts empty. BEFORE CALLING: - Work out which country the user's business is in. Use it if the user has said, or if you already know where they are. Otherwise, ask them. If they don't say, call without country. AFTER CREATING: - To show the user the store, call theme_screenshot on its home page, as the result says: its widget has a View button that opens the preview. Until the store is saved to a Shopify account, don't show or link its domain to the user: it's only the store's ID for tool calls, and opening it in a browser doesn't show the preview. - To make changes to the store, pass its domain as store to graphql_schema, graphql_query and graphql_mutation. They are the only tools that work on it, including for adding products: the other store tools need a sign-in and start one. Anyone with this store's address can view and edit it, and can get a link to save it, until it's saved to a Shopify account. Tell the user so, and that saving it keeps it. The preview link works for about 30 minutes. When the user wants to see the store again, its products or a change you made after that, call get_preview_store_links with its domain and give them the new preview link. That call also gets a link to save the store to a Shopify account.

finalize-digital-file-attachment

ChatGPT
Record a digital file that was uploaded directly to storage by the widget, then enable automatic delivery for the variant. Called only by the widget after a successful upload to the URL from attach-digital-file; never invoke directly from the model. Does not publish the product.

finalize-digital-product-media

ChatGPT
Attach a media image that was uploaded straight to storage by the widget, as the digital product's media. Called only by the media image upload widget after a successful upload to the target from attach-digital-product-media; never invoke directly from the model. Leaves the price, description, status and attached digital file untouched, and does not publish the product.

finalize_file_upload

ChatGPT
Create a file in the shop's Files from an upload the widget sent straight to storage. Called only by the upload-file widget after a successful upload to the target from stage_file_upload; never invoke directly from the model.

find-mock-shop-catalogs

ChatGPT
Find ready-made sample catalogs (from mock.shop) that fit the merchant's business, so they can pick one to seed their store with realistic products and collections instead of starting empty. WHEN TO USE: - The merchant has a new or empty store and wants sample products, a starter catalog, demo data, or "something to look at" before adding their own products. - The merchant describes what they sell (or plan to sell) and wants a store populated quickly. WHEN NOT TO USE: - The merchant wants one-off placeholder products rather than a whole catalog — use find-sample-product. - The merchant wants real products to source or resell — this returns sample data, not supplier inventory. - The merchant wants to browse products already in their store — use search-products. INPUT: a short description of the business or what it sells (e.g. "handmade soy candles", "supplies for a new puppy", "streetwear for teens"). Take it from what the merchant said. If they gave no hint at all, ask one question — what do they plan to sell? — then call. OUTPUT: up to limit catalogs (default 3), best match first. Each has a name, short description, categories, collection titles, product and collection counts, currency, and a storefrontUrl the merchant can open to browse it as a live storefront. Present them as a short list with the storefront links and ask the merchant which one they want. Pass the chosen catalog's subdomain to import-mock-shop-catalog to copy it into their store. An empty list means nothing matched well — suggest the merchant describe their business differently.

find-sample-product

ChatGPT
Find placeholder sample products that help a merchant visualize a store or get product inspiration. These are placeholder examples, not real supplier inventory. WHEN TO USE: - The user explicitly asks for sample, example, placeholder, or mock products. - The user wants inspiration to visualize a store rather than products to source or import. WHEN NOT TO USE: - The user wants real products they can source, import, or sell. This tool returns placeholders, not sourceable inventory. - The user wants to browse products that already exist in their store — use search-products. - The user wants to create their own product listing from a description — call create-product directly. INPUT — the ONLY thing you need from the user is a product or category: - As soon as the user asks for samples or inspiration and names a product or category, call the tool immediately with it. Do not ask anything else. - Do NOT ask about style, audience, price, brand, quantity, or any other detail — the widget refines everything through its own search bar. - ONLY if the user asked for samples or inspiration but gave no product or category, ask a single question: what kind of products are they thinking of? Then call the tool. Never ask more than this one question. Each card has an 'Add this product' button. When the user clicks it, the widget adds that sample product to their store on its own — you do not need to take any further action.

find_chat_file_upload

ChatGPT
Check whether a file from the chat is already in the shop's Files. Called only by the upload-file widget before it uploads a file from the chat; never invoke directly from the model.

generate-business-names

ChatGPT
Generate business name ideas for someone starting a Shopify store. WHEN TO USE: - The user wants name ideas for a new business or store. - The user has described a business but has not named it yet. - The user has a name and wants alternatives in the same vein. WHEN NOT TO USE: - The user already knows the name they want and only needs to set it — that is done in the Shopify admin, not here. - The user wants a product name, a slogan, or a tagline rather than a business name. INPUT: a short description of the business in the user's own words — what they sell, who it is for, or the feeling they want ('hand-poured soy candles for dark, woody scents'). Max 255 characters. Pass what the user actually said; do NOT invent a business they have not described. Every name comes back with a signupUrl, the link that acts on it, so present it rather than describing it. Where it goes depends on the user: with no Shopify store connected it opens store signup with the name already filled in; with a store connected it opens the store name setting in that store's Shopify admin, where they save the new name themselves. Either way the tool only hands back a link — it creates and renames nothing. A store name is not exclusive, so the user can take any of these for their store. Nothing here is verified, though — no trademark search, no business registry, no check of whether someone else is already trading under the name — so tell them to check that before building a brand on it.

generate-domain-names

ChatGPT
Suggest available domain names for a new Shopify store. Every domain returned has been checked against the domain registry and was available at the time of the call. WHEN TO USE: - The user wants a domain for a business or store name. - The user's preferred domain is taken and they want alternatives. - The user asks whether a domain idea is available. - The user wants to know what a domain costs. - The user wants to buy or register a particular domain. WHEN NOT TO USE: - The user wants to connect or troubleshoot a domain they already own — that is done in the Shopify admin, not here. - The user only wants store-name ideas and does not care whether a domain is available or what it costs. INPUT: a store name, a domain the user has in mind, or a short description of the business. All three work. If the user named a domain, the tool checks that exact domain, checks the same name at other common TLDs, and also returns 3 alternatives. An unusual TLD is fine — keep the one the user said. Pass the domain on its own as the query, or — when it sits inside a sentence — put it in exactDomain. If the user named no domain, put the words the domain should be built from in storeName: a name the user proposed ('volcanic balloon', 'Ember & Oak'), or the subject of what they described ('a domain about hippos, giraffes, and iguanas' → 'hippos giraffes iguanas'). Four words at most, lead-in and connecting words dropped, in the user's own words rather than converted to a domain yourself. The tool compresses them into a domain and checks that the same way; without storeName there is no availability check for a query like that, only suggestions. Only the exact domain checked can come back unavailable. Every other domain returned is available to buy, so do not describe any of them as taken, and do not say which TLDs were checked — an unlisted TLD may have been taken or may not have been quoted, and you cannot tell which. Availability is a point-in-time check, not a hold. Tell the user to register a domain they want promptly, and never promise a domain is still available later in the conversation. Prices, where present, are the registry's quote for the first registration term in the stated currency. Renewal is priced separately and is often higher, so present a price as what registering costs today, not as an ongoing rate. A domain can come back without a price; say nothing about its cost rather than guessing, and in particular do not read a missing price as a domain that costs nothing. Every domain here has to be bought. Say a domain is "available" or "unavailable" — never that it is "free", which states a price rather than an availability and states it wrongly. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-collection

ChatGPT
Retrieve detailed information about a specific Shopify collection by its GID, including title, description, image, products, and rules (for smart collections). MUST be called whenever the user refers to a collection they own or previously created — regardless of phrasing. Trigger phrases include: "my collection", "that collection", "the collection", "show me my collection", "get my collection", or any reference to a previously created or known collection. "Show" and "get" mean the same thing here: always fetch live data from Shopify. Do NOT rely on memory or prior responses — always call this tool for the source of truth. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-collective-import-availability

ChatGPT
Report whether this store can import Collective products right now, and whether a product handed to the managed install flow has been imported. Called only by the Collective product shelf widget while it waits for an install started from the shelf to finish.

get-collective-product

ChatGPT
Load current details for one Collective product shown in the Collective product shelf. Called only by the shelf widget.

get-digital-file-attachment

ChatGPT
Read which file a Digital Products variant delivers now. Called by the upload widget before it takes a file from the chat, not by the model. Changes nothing.

get-digital-product

ChatGPT
Show the merchant a card for a digital product: its media image, title, price, status, and what the buyer receives. Call this after each step of the digital product flow — after the price is set, after the file is attached, after the media image is added, and after publishing — so the merchant sees the listing as it stands. Every field is read back from Shopify, so the card is current rather than a summary of what was asked for. This only reads. It changes nothing about the product.

get-digital-products-install-status

ChatGPT
Report whether the Digital Products app is installed on the authenticated store. Used by the install widget to poll while the merchant completes the Shopify Admin install flow.

get-inventory-levels

ChatGPT
Retrieve inventory levels for all variants of a product across locations. Use this when the user asks about stock quantities, inventory availability, or wants to see how much inventory is at each location for a given product. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-new-store-previews

ChatGPT
Generate a new Shopify shop based on three short fields describing the store, plus an explicit attestation that the user wants a brand-new store. WHEN TO USE: - User wants to create a new storefront - User wants to generate a store design - User wants to preview a store layout WHEN NOT TO USE: - User wants to edit or modify an existing theme — this tool cannot edit themes - User wants to add a generated theme to a store they already own — previews can only be claimed as brand-new stores - User wants to customize a live storefront's design IMPORTANT: This tool takes FOUR required fields — productOrService, targetAudience, brandStyle (each compressed from what the user said), and userUnderstandsNewStoreOnly. See the userUnderstandsNewStoreOnly field's own description for the rules on when to set it silently versus when to confirm with the user first; do not invent a confirmation step when none of those rules apply. Do NOT invent values for the descriptive fields. If the user has not told you what they sell, who their customers are, or what visual style they want, ASK THEM before calling this tool. Make sure you have enough concrete detail from the user that there's something meaningful to compress — at least varieties or specifics for the product, real audience traits, and concrete visual cues. The previews are much better when each field is grounded in something the user actually said. Each descriptive field (productOrService, targetAudience, brandStyle) is a comma-delimited keyword phrase (max 78 characters), compressed from what the user said — no synonyms, no inferred attributes, no full conversation history. Drop filler words and keep nouns and concrete descriptors. Returns up to 3 storefront previews. Generation typically takes about 3 minutes. After calling this tool, let the user know their previews are on the way and may take a few minutes. Remind them that the previews can only be claimed as brand-new stores; they cannot be applied to an existing storefront or used to edit an existing theme. Keep the conversation going while they wait. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-order

ChatGPT
Retrieve detailed information about a specific Shopify order including line items, fulfillment status, shipping address, and tracking. Use this when the user asks about a particular order's details or status. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-product

ChatGPT
Retrieve detailed information about a specific Shopify product by its GID, including title, status, vendor, variants, images, tags, and inventory. MUST be called whenever the user refers to a product they own or previously created — regardless of phrasing. Trigger phrases include: "my product", "that product", "the product", "show me my product", "get my product", "pull up the product", "open my product", or any reference to a previously created or known product. "Show" and "get" mean the same thing here: always fetch live data from Shopify. Do NOT rely on memory or prior responses — always call this tool for the source of truth. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-shop-info

ChatGPT
Retrieve basic information about the connected Shopify store including name, domain, email, plan, currency, timezone, and country. Use this when you need store context to tailor advice (e.g. plan limitations, currency for pricing, timezone for scheduling), when the user asks about their store details, or to verify which store is connected. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

get-storefront-generation

ChatGPT
Get the current state of a storefront generation. Used by the widget to poll for preview completion.

get_uploaded_files

ChatGPT
List the files added to the store's Files since the since value upload_file returned, whether the merchant finished the upload in the upload box or in Shopify admin, with each one's URL. Call this when the merchant says their upload is done, passing the since value upload_file returned. The widget cannot tell this conversation when the upload finishes on every host, so this is how you learn the result. If the upload widget already gave you the file ID and URL, use them; otherwise call get_uploaded_files with the since value upload_file returned. Lead with the file's URL when you tell the merchant; you can offer its Shopify admin link second. Never show file IDs or gid:// values; keep them for tool calls.

graphql_mutation

ChatGPT
Execute a GraphQL mutation against the Shopify Admin API. The Shopify Admin API supports hundreds of mutations. Built-in tools cover common write operations, but when the user asks to modify a resource that has no dedicated tool (e.g. metafields, metaobjects, pages, blogs, translations, publications, etc.), use this tool. Note: Some dangerous mutations are blocked for safety (e.g. refunds, gift card writes, staff management, theme deletion, theme publishing). Theme file writes (themeFilesCopy, themeFilesUpsert) are allowed on unpublished themes only — writes that target the live/MAIN theme are blocked. If a mutation is blocked, inform the user and suggest they perform the action in Shopify admin. The host app will prompt the user for confirmation before executing. Before calling this tool, follow the GraphQL Workflow: 1. Use graphql_schema to look up the exact mutation name (type_name='Mutation') and input type fields — do NOT guess. 2. You can also use search_docs_chunks to find mutation examples in Shopify documentation. 3. Construct the operation. 4. Call validate_graphql_codeblocks to verify the operation — do NOT skip validation. 5. Only then call this tool to execute the mutation. IMPORTANT: After executing, present the results clearly to the user. Do NOT dump raw JSON — summarize what changed in a helpful, readable way.

graphql_query

ChatGPT
Execute a read-only GraphQL query against the Shopify Admin API. The Shopify Admin API exposes hundreds of resources. Built-in tools cover common operations, but when the user asks about a resource that has no dedicated tool (e.g. gift cards, metafields, metaobjects, pages, blogs, markets, translations, publications, etc.), use this tool to fetch the data. Before calling this tool, follow the GraphQL Workflow: 1. Use graphql_schema or search_docs_chunks to discover the correct types and fields — do NOT guess field names. 2. Construct the operation. 3. Call validate_graphql_codeblocks to verify the operation — do NOT skip validation. 4. Only then call this tool to execute the query. Pagination: include pageInfo { hasNextPage endCursor } in your query. Pass the endCursor value as the after variable for the next page. IMPORTANT: After calling this tool, present the results clearly to the user. Do NOT dump raw JSON — summarize the key information in a helpful, readable way.

graphql_schema

ChatGPT
Explore the Shopify Admin GraphQL schema to discover types, fields, and arguments. You MUST use this tool before calling graphql_mutation to look up the exact mutation name and input type fields. Pass a type name to inspect. Common starting points: - 'Mutation' — list all available mutations (search here first for mutations) - 'QueryRoot' — list all available queries - 'Product', 'Order', 'Customer' — inspect entity fields for queries - 'ProductInput', 'ProductVariantInput' — inspect mutation input types Workflow for mutations: graphql_schema('Mutation') → find the mutation → graphql_schema('InputTypeName') → construct the mutation → validate_graphql_codeblocks → graphql_mutation. Workflow for queries: graphql_schema('QueryRoot') → find the query → graphql_schema('TypeName') → construct the query → validate_graphql_codeblocks → graphql_query. You can also use search_docs_chunks to find examples in Shopify documentation.

import-collective-product

ChatGPT
Check availability and queue one Collective product for import, or return the required next step. Reports alreadyImported when the store already has the product. Called only by the Collective product widget.

import-mock-shop-catalog

ChatGPT
Copy a mock.shop sample catalog's starter set — its first 2 collections and up to 8 products from each (with variants, prices, images), so at most 16 products — into the merchant's connected store, publishing everything to the Online Store. Use it after the merchant picks a catalog from find-mock-shop-catalogs. One call does the whole import. RE-RUNNING IS SAFE AND NEVER OVERWRITES: calling again (after a timeout or partial: true) adds only what is missing — products not yet imported, memberships and publications not yet made. A product already imported from this catalog is left exactly as it is — including any edits the merchant has made since, and including whether it is published — and counted under unchanged; if it is not published, it is listed under unpublished for the merchant to publish or delete in Admin. A product the merchant already has at the same handle from elsewhere is left untouched and reported under skipped. A collection the merchant already has at the same handle is reused when its title matches the catalog's (missing imported products are added to it) and skipped when it does not. Collections are created only with their imported products, so none is ever left empty. INPUT: subdomain from the chosen catalog (e.g. "pets"). Nothing else. OUTPUT: counts of products created/unchanged/skipped and collections created/reused/skipped, and currency. If partial is true Shopify rate-limited the call: wait a few seconds, then call again with the same subdomain. Prices are copied as plain amounts; when currency.mismatch is true tell the merchant prices came from a ${currency.source} catalog and were not converted, so they should review them.

list-customers

ChatGPT
Retrieve a list of customers from the connected Shopify store, including name, email, phone, order count, and total spent. Use this when the user asks about their customers, wants to look up a specific customer, or needs customer data for analysis. SEARCH SYNTAX: When the user is looking for a specific customer (by name, email, tag, etc.), ALWAYS pass a structured query using Shopify's customer search syntax. Do NOT pass a bare free-text term like Smith for a name search — Shopify's default fields match addresses, tags, company names, and notes, which returns unrelated customers. Field filters use field:value. Combine with AND / OR / NOT; parenthesize subqueries. Ranges use :<, :<=, :>, :>= on numeric / date fields. Name lookups should query BOTH first and last name, e.g. for "customers named Smith" use first_name:Smith OR last_name:Smith. Supported filter fields: - Name: first_name, last_name - Contact: email, phone - Location: country (full name or code, e.g. Canada / CA) - Account state: state (enabled | invited | disabled | declined) - Marketing: accepts_marketing (boolean), email_marketing_state (subscribed | not_subscribed | pending | invalid | redacted) - Tags: tag, tag_not - Numeric (support ranges): orders_count, total_spent, id - Date (support ranges): created_at, updated_at — use ISO 8601 in quotes, e.g. created_at:>'2024-01-01' Examples: - Find customers named Smith → first_name:Smith OR last_name:Smith - Customers with gmail addresses → email:*@gmail.com - Customers with more than 5 orders → orders_count:>5 - Customers from Canada → country:Canada - VIP customers → tag:vip - Subscribed to email → email_marketing_state:subscribed IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed above. Do NOT invent fields like name:, full_name:, customer_name:, or city:. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

list-orders

ChatGPT
Retrieve recent orders from the connected Shopify store. Returns order name, customer, totals, financial and fulfillment status. Use this when the user asks about their orders, wants an overview of recent sales, or needs to find a specific order. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

open-digital-products-install

ChatGPT
Open a Shopify Admin install handoff for Digital Products on the authenticated store. Use this only after the merchant has explicitly asked to install or prepare Digital Products for their store. The app identity is fixed by Shopify; this tool cannot install arbitrary apps and does not install anything silently. The merchant must click the widget button and complete the Shopify Admin install flow before Digital Products connector tools can continue.

publish-digital-product

ChatGPT
Take a draft digital product live through Shopify Digital Products, so buyers can purchase and download it. Activates the product and requests its Online Store listing. Refuses to publish a product with nothing attached, so attach the file first with upload-digital-product-file. Digital Products does not report whether the Online Store listing succeeded, so tell the merchant to check the product in their Online Store if buyers cannot find it.

refresh-collective-products

ChatGPT
Report current import availability and per-product offer terms for products already shown in the Collective product shelf. Called only by the shelf widget to reconcile a shelf rendered before Shopify Collective was installed.

report-digital-file-upload

ChatGPT
Record the outcome of a file upload the widget sent straight to storage. Called only by the upload widget; never invoke directly from the model. Records telemetry and changes nothing about the product.

run-analytics-query

ChatGPT
Run a ShopifyQL analytics query. Returns tabular results with automatic chart visualization. IMPORTANT: Always use FROM...SHOW syntax. Use TIMESERIES for time charts, GROUP BY for categories. Sales & Revenue - FROM sales SHOW gross_sales TIMESERIES day SINCE -30d UNTIL today - FROM sales SHOW orders, gross_sales, discounts, returns, net_sales, shipping_charges, taxes, total_sales TIMESERIES day SINCE -30d UNTIL today - FROM sales SHOW total_sales TIMESERIES day SINCE -30d UNTIL today COMPARE TO previous_period - FROM sales SHOW gross_sales, discounts, returns, net_sales, shipping_charges, taxes, total_sales - FROM sales SHOW average_order_value TIMESERIES day SINCE -30d UNTIL today Orders - FROM sales SHOW orders TIMESERIES day SINCE -7d UNTIL today - FROM fulfillments SHOW orders_fulfilled, orders_shipped, orders_delivered TIMESERIES day SINCE -30d UNTIL today Products - FROM sales SHOW gross_sales, net_sales, orders GROUP BY product_title ORDER BY gross_sales DESC LIMIT 10 - FROM inventory SHOW starting_inventory_units, ending_inventory_units, inventory_units_sold, sell_through_rate GROUP BY product_title, product_variant_title Customers - FROM sales SHOW returning_customers, customers, returning_customer_rate TIMESERIES day SINCE -30d UNTIL today - FROM customers SHOW new_customers, returning_customers TIMESERIES day SINCE -30d UNTIL today Sessions & Conversion - FROM sessions SHOW sessions, online_store_visitors TIMESERIES day SINCE -30d UNTIL today - FROM sessions SHOW sessions, sessions_with_cart_additions, sessions_that_reached_checkout, sessions_that_completed_checkout, conversion_rate TIMESERIES day SINCE -30d UNTIL today - FROM sessions SHOW sessions GROUP BY session_device_type SINCE -30d UNTIL today - FROM sessions SHOW sessions GROUP BY session_country SINCE -30d UNTIL today Marketing & Referrals - FROM sales SHOW orders, total_sales GROUP BY order_referrer_source, order_referrer_name SINCE -30d UNTIL today - FROM sessions SHOW sessions WHERE referrer_source = 'social' GROUP BY referrer_name SINCE -30d UNTIL today Tables: sales, orders, sessions, customers, fulfillments, inventory, payments Time grouping: TIMESERIES day/week/month. Category grouping: GROUP BY column Comparison: COMPARE TO previous_period. Aggregates: WITH TOTALS, PERCENT_CHANGE IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

search-collective-product-candidates

ChatGPT
Find and judge Shopify Collective products PRIVATELY before showing one selected shelf. This is the only entry point for real supplier products a merchant wants to source, import, or sell. A request for products "I can sell" means real supplier products: ALWAYS use this tool, never placeholder samples, unless the user explicitly asks for samples, examples, placeholders, or mocks. Use it for straightforward concrete product requests as well as curation, recommendations, audiences, themes, aesthetics, store ideas, and refinements. The user does not need to say "curate." Never expose raw or intermediate search results. HARD QUERY LIMIT: make ONE initial call with a queries array; attempt defaults to INITIAL when omitted. For a broad brief, choose 1–3 independent product lanes upfront; the server searches them concurrently. For a precise product-type brief, include exactly ONE query. Wait for the entire result before selecting, correcting, or calling show-collective-products. Never issue multiple candidate-tool calls in one assistant turn or another initial batch. Only when the whole batch has NO on-brief candidates may you make ONE corrective call with attempt CORRECTION and exactly ONE new query. Mixed relevant/irrelevant results and empty lanes beside on-brief lanes do not earn a correction. Never exceed FOUR queries total (not four batches). Stop after the correction, and stop immediately after any upstream failure, including a rate limit. For a broad audience/theme brief, put distinct concrete 2–5 word product-noun searches in the same queries array, not vague vibes or synonym rewrites. Explore different product types that fit the brief. Choose only the independent lanes needed; three is a maximum, not a target. Compare all returned candidates globally, discard weak lanes, avoid near-duplicates, and prefer no more than two products from one vendor. Begin searching rather than only listing hypothetical product ideas. For a concrete product request, search its product type and useful attributes first, with exactly one query in the array. If even ONE candidate matches every explicit constraint, finalize immediately without another search. Never spend the broad three-query budget on a precise brief or search to add variety. If the private search has no matches, use only the single corrective call. To broaden retrieval: try a simpler product noun, a parent category, or another relevant angle instead of repeating the unsuccessful query. Broader retrieval is not permission to relax selection constraints: preserve explicit product type, color, material, and exclusions when choosing the final IDs. Explore adjacent product types only when the brief leaves the type open. Prefer fewer relevant products over padding, and ask before relaxing a hard constraint if no matches remain. For refinement, reuse candidates already in context when they satisfy the feedback. Otherwise search broader relevant lanes privately. Never reintroduce rejected products or display interim shelves while trying new angles. Select only candidate IDs you observed. Call show-collective-products once with at most 10 ordered IDs after the batch results have returned and you have selected across the candidates. Never call the finalizer in the same assistant turn as a candidate search. These searches do not render a shelf; do not narrate their individual products to the user. Never call show-collective-products with an empty selection. If the bounded search and correction produce no on-brief candidates, stop without rendering a shelf and follow the fallback instruction in the tool result. When verified market context is available, a result for a connected store outside the US includes a market-specific catalog advisory. This is best-effort guidance, not an eligibility decision: continue the normal bounded workflow without asking for extra confirmation. Do not assume an absent advisory means the store is US-based.

search_collections

ChatGPT
Search and browse collections on a Shopify store. Use this whenever the user wants to see, find, or look at collections in their store. Trigger phrases include: 'show me my collections', 'what collections do I have', 'list my collections', 'find a collection', 'search collections', or any reference to viewing multiple collections. 'Show' and 'get' mean the same thing: always fetch live data from Shopify. Do NOT summarize from memory. Use this when the user wants to: - list or search collections - find a collection by name - check what collections exist in their store - find a collection GID to use with add-to-collection or create-product Returns collection data from the connected store via the Shopify Admin API. Results are capped at 50 per call. When pageInfo.hasNextPage is true, more matches exist than were returned. Tell the user you are showing the first N results and offer two paths: (a) load more via after: pageInfo.endCursor, or (b) refine the search with a stricter query. Only act on one of those paths when the user asks; do not auto-paginate. SEARCH SYNTAX: Free text matches across default fields (e.g. summer, "new arrivals"). Field filters use field:value. Combine with AND / OR / NOT; parenthesize subqueries. Ranges use :<, :<=, :>, :>= on numeric/date fields. Example: collection_type:smart AND title:sale*. IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed below, as flat names. Do NOT invent dotted paths like collection.title or rules.column. Supported filter fields: - Text / exact: title, handle, collection_type (custom|smart) - Numeric (support ranges): id - Date (support ranges): updated_at, published_at — use ISO 8601 in quotes, e.g. updated_at:>'2024-01-01' - ID: product_id (collections containing the given product) - Publication: published_status (e.g. published, unpublished, online_store_channel) Note: there is no server-side filter for product count, rules, or sort order. For those, filter by collection_type and inspect the returned productsCount / sortOrder fields client-side, or narrow with title: / handle:. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

search_docs_chunks

ChatGPT
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.

search_products

ChatGPT
Search and browse products on a Shopify store. MUST be called whenever the user wants to see, find, or look at products in their store. Trigger phrases include: 'show me my products', 'what products do I have', 'list my products', 'browse my catalog', 'find a product', 'search for', or any reference to viewing multiple products. 'Show' and 'get' mean the same thing: always fetch live data from Shopify. Do NOT summarize from memory. Use this when the user wants to: - list or search products - look up a specific product by ID or handle - check product status or details - browse what's in their catalog Returns product data from the connected store via the Shopify Admin API. Results are capped at 50 per call. When pageInfo.hasNextPage is true, more matches exist than were returned. Tell the user you are showing the first N results and offer two paths: (a) load more via after: pageInfo.endCursor, or (b) refine the search with a stricter query. Only act on one of those paths when the user asks; do not auto-paginate. SEARCH SYNTAX: Free text matches across default fields (e.g. shoes, "green hoodie"). Field filters use field:value. Combine with AND / OR / NOT; parenthesize subqueries. Ranges use :<, :<=, :>, :>= on numeric/date fields. Example: price:<=25 AND status:active. IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed below, as flat names. Do NOT invent dotted paths like variants.price, product.tag, or variant.sku. Supported filter fields: - Text / exact: title, vendor, product_type, handle, sku, barcode, variant_title, tag, tag_not, status (active|archived|draft) - Numeric (support ranges): price (matches products with ANY variant whose price satisfies the condition), inventory_total, id, variant_id - Date (support ranges): created_at, updated_at, published_at — use ISO 8601 in quotes, e.g. created_at:>'2024-01-01' - Boolean: gift_card, bundles, is_price_reduced, out_of_stock_somewhere, tracks_inventory, has_only_default_variant - ID: collection_id, category_id Price examples (cross-variant semantics): - price:<=25 — products with at least one variant priced $25 or less - price:>100 price:<=500 — products with at least one variant in $100–$500 - price:25 — products with at least one variant priced exactly $25 For a min/max of every variant or a product-wide price band, this tool cannot express it server-side; tell the user and suggest narrowing with price: plus another filter (e.g. product_type:, vendor:, tag:). IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

set-inventory

ChatGPT
Set the available inventory quantity for a specific inventory item at a given location. Always call get-inventory-levels first to get the inventoryItemId, locationId, and current available quantity. Pass the current quantity as compareQuantity so the update fails safely if stock changed since you read it. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

shopify-app

ChatGPT
Open the integrated Shopify app.

show-collective-products

ChatGPT
Render one curated Shopify Collective product shelf from canonical product IDs. Call this only after the entire search-collective-product-candidates batch has returned and you have privately judged its candidates, or when refining IDs already shown in a prior Collective shelf. Never call this in the same assistant turn as a candidate search. Supply 1–10 IDs in the exact display order. Use only IDs you observed; do not invent or alter IDs. The server re-fetches canonical, currently visible product data, removes duplicates, and omits stale, ineligible, or non-displayable products. It does not require conversation history, so a valid visible ID can be finalized regardless of which Collective search first returned it. The title is a short user-facing shelf heading. productIds must be a JSON array of ID strings, never one JSON-encoded string. Pass IDs rather than product objects. Call this once per curation attempt. If every selected ID has become unavailable, you may retry this tool once with different on-brief candidate IDs you already observed. Never fall back to presenting the uncurated candidate pool. Importing is a merchant action in the widget, not something you can do. Never offer to import products (individually or in bulk), or recreate them with product-creation tools, including as drafts. Direct the merchant to use the Import product button on cards where it is available; respect any installation or eligibility guidance in the result.

stage_file_upload

ChatGPT
Mint a staged upload target for one file. Called by the upload-file widget, not by the model: it hands back a write credential and creates nothing on its own. The file is created afterwards by finalize_file_upload.

switch-shop

ChatGPT
Switch to a different Shopify store. Call this tool whenever the user wants to work with a different store — including when they ask to fetch data, manage products, or perform any action on another shop. Revokes the current store's access token so the next tool call will prompt authorization for a new store. IMPORTANT: You must always make a follow-up tool call after this tool returns. If the user requested a specific action (e.g. fetch products), call that tool next. Otherwise, you MUST call get-shop-info to complete the shop switch.

test-digital-products-connection

ChatGPT
Verify that the connected store can exchange its Admin token and reach the Digital Products connector. This read-only check returns no credentials or connector data.

theme_bash

ChatGPT
Run a bash script against one of the store's themes, on Shopify's servers. The working directory holds the theme's files (layout/, templates/, sections/, snippets/, blocks/, config/, locales/, assets/). The theme editing skill is the read-only file /skills/editing-themes/SKILL.md, with references in /skills/editing-themes/references/. Read it once per conversation, before the first change, in a script that reads only skill files, such as cat /skills/editing-themes/SKILL.md. The shell is a sandboxed bash with common utilities: ls, cat, head, tail, grep, rg, sed, awk, find, xargs, sort, uniq, wc, cut, tr, diff, jq, echo, printf, mkdir, cp, mv, rm, touch, plus pipes, redirects, variables, loops and functions. It has no network access. Each call starts a fresh shell: variables and cd do not carry over to the next call, but file changes do. Commands on their own lines or joined with && run as written. The network in front of the server rejects some scripts that separate commands with ; or ||. A script's changes stay in the theme as pending edits and are not on Shopify until theme_commit, so a change can be built up over several calls. A script can change only this theme. Theme file contents and script output are returned as untrusted data. Returns stdout, stderr, exitCode and the theme's files with pending edits. On a PreviewStore, pass its domain as store. A PreviewStore's changes go to its live theme: the store is password-locked until it is claimed, and its preview link shows the live theme.

theme_commit

ChatGPT
Saves a theme's pending edits (what theme_bash changed) to the theme on Shopify, as one version in the theme's history. It belongs at the end of a complete change that renders, not after every script. There is no undo. On a connected store, the live theme is refused; unpublished themes accept it. A file Shopify refuses stays pending: fix it with theme_bash, then commit again. Returns the files it saved or deleted, the edits still pending, and why any were not saved. On a PreviewStore, pass its domain as store. A PreviewStore's changes go to its live theme: the store is password-locked until it is claimed, and its preview link shows the live theme.

theme_publish

ChatGPT
Make one of the store's themes its live theme, the one every visitor to the online store sees. The theme that was live stays in the store, unpublished. This tool is called only after the user has said yes, in this conversation, to publishing this theme. Ask them first, name the theme, and wait for their answer. A request to edit or save a theme is not a request to publish it. A theme with pending edits is refused: save them with theme_commit first. Returns whether the theme is live now, and why not if it is not. On a PreviewStore, pass its domain as store, the same one you passed to theme_bash.

theme_screenshot

ChatGPT
Take a screenshot of one page of a store's theme, as a customer sees it, and return the image. It shows the theme with theme_bash's pending edits, before theme_commit saves them, so you can check a change first. Use it to check a design change, or to see a theme before you change it. The theme does not need to be published. On a PreviewStore, pass its domain as store, the same one you passed to theme_bash. Without store, it shows a theme on the connected store, which doesn't have a PreviewStore's themes.

theme_screenshot_viewport

ChatGPT
Take the same theme_screenshot page at the other size, for the screenshot widget's size switcher.

update-collection

ChatGPT
Update an existing collection's title, description, image, sort order, or rules. Use this when the user wants to modify, change, or edit collection details. Trigger phrases include: "update my collection", "change the collection", "edit the collection", "rename the collection". IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you have a local file, generated image, or external URL: call the upload-image tool FIRST to get a permanent Shopify CDN URL, then pass that URL here. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real collections. SMART COLLECTION RULES: - Pass ruleSet to update the rules for a smart collection. - Common rule columns: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE. - Common relations: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN. - Passing ruleSet replaces all existing rules. Omitting it leaves rules unchanged. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

update-product

ChatGPT
Update an existing product's title, description, status, images, variant pricing, or variant option values (e.g. color, size names). Use this when the user wants to modify, change, or edit product details — including status, variant prices, option values, or images. Trigger phrases include: 'update my product', 'change the price', 'edit the product', 'modify my product', 'rename the variant', 'change the color name'. IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you have a local file, generated image, or external URL: call the upload-image tool FIRST to get a permanent Shopify CDN URL, then pass that URL here. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real products. REPLACING IMAGES: - To replace specific images, first use get-product to find the mediaId of the image(s) to remove. - Pass those mediaId values in removeMediaIds, and provide the new images in the images array. - To remove images without adding new ones, pass removeMediaIds without images. IMPORTANT: This tool already presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps. Always list out some potential next actions for the user to take.

update-product-interactive

ChatGPT
Open an interactive product editing app for an existing product in the connected Shopify store. Use this when the user wants to review or edit an existing product before saving changes. Pass the product id, the product title and description the panel should show and eventually save, and a variant id when proposing a first-variant price update. The tool fetches the current product images first, removes any removeMediaIds, appends any images, and renders the resulting draft media list. The product panel renders the product title, description, draft images, and first variant price. When the merchant saves, the app sends reviewed text fields and first-variant price changes through to update-product. A call only re-seeds the app, so do not report a change as saved until the merchant saves it. While the app holds a product, leave that product's title, description, and first-variant price to it rather than writing them with update-product, because the merchant's next Save would overwrite you. Every other field, including status and the product's other variants, is still yours to update directly when the user asks for it.

upload-digital-product-file

ChatGPT
Open a file picker so the merchant can attach the downloadable file to a digital product they have already created. Call this after create-digital-product, passing back the product and variant identifiers it returned. The merchant chooses the file and their browser sends it directly to Shopify's storage; the file contents never pass through this conversation. This attaches the file to an existing draft product. It does not create products and does not publish anything.

upload-digital-product-media

ChatGPT
Open an image picker so the merchant can add a media image to a digital product they have already created. Ask the merchant whether they want a media image first, and only call this if they say yes. A digital product sells perfectly well without one. The merchant chooses the image and their browser sends it directly to Shopify's storage; the image never passes through this conversation. This adds an image to an existing draft product. It does not change the price, description, attached file or status, and it does not publish anything.

upload-image

ChatGPT
Upload an image, photo, or media file to Shopify and get a permanent CDN URL. ALWAYS use this tool before create-product or update-product when you have a local file, generated image, or external URL that needs to be hosted on Shopify. This is the ONLY way to attach, host, or store images on Shopify — create-product and update-product cannot accept local file paths directly. WHEN TO USE: - You generated an image or the user pasted/uploaded one — pass it via the 'image' parameter. - You have an external HTTPS image URL and want a stable Shopify-hosted copy — use sourceUrl. - The user says: 'upload', 'attach', 'add image', 'add photo', 'host image', 'store image', 'upload file', 'upload media', 'add a picture', or similar. - Another tool (create-product, update-product) rejected a local file path — call this tool first to get a CDN URL. INPUT (provide exactly one of image or sourceUrl): - image: A file reference (e.g. local file path like /mnt/data/image.png). The host app transforms this into a downloadable URL automatically. THIS IS THE PREFERRED METHOD for generated or uploaded images. Pass the bare file reference — do not construct or echo a file object yourself. - sourceUrl: A publicly accessible HTTPS URL of the image to re-upload to Shopify. Must be reachable by Shopify's servers; private, signed, or host-internal URLs (e.g. presigned blob URLs from your own runtime) are not supported — use the 'image' parameter for those. OUTPUT: - A permanent Shopify CDN URL that can be passed to create-product or update-product image fields. WORKFLOW: 1. Call upload-image with the file or URL. 2. Use the returned CDN URL in create-product or update-product image fields.

upload_file

ChatGPT
Open a file picker so the merchant can upload an image or file from their own device to the store's Files, and get back its Shopify URL. Use this when the merchant wants to upload something that is on their computer or phone: a product photo, a logo, a PDF. Not for a file the merchant is selling as a digital download; that goes through create-digital-product and upload-digital-product-file, which keep it private until purchase. If the file is already in this chat — the user attached it or you generated it — use upload-image instead; this tool cannot see chat files. The merchant chooses the file and their browser sends it directly to Shopify's storage; it never passes through this conversation. Nothing tells this conversation when the upload finishes. End your reply by asking the merchant to tell you when it is done. Do not say or imply that you are watching for it. THE WIDGET CHANGES STATE AFTER YOU RETURN: when the merchant finishes the upload, the widget pushes the file's URL and file ID to you as an app context update. Read it before your next action; it is newer than this tool result. If it isn't there, call get_uploaded_files with the since value this tool returns. If the upload widget already gave you the file ID and URL, use them; otherwise call get_uploaded_files with the since value upload_file returned. Lead with the file's URL when you tell the merchant; you can offer its Shopify admin link second. Never show file IDs or gid:// values; keep them for tool calls. To add an uploaded image, video or 3D model to an existing product without Shopify copying it, call graphql_mutation with mutation { fileUpdate(files: [{ id: "<file GID>", referencesToAdd: ["<product GID>"] }]) { files { id } userErrors { field message code } } }. Never add an uploaded file to a product by its URL (productCreateMedia, media in productUpdate or productSet, update-product images, or any originalSource): each makes a copy of the file.

use_skill

ChatGPT
Lists and reads this server's skills: step-by-step guides to load before the work they cover. Call with no arguments to list each skill's frontmatter and files. Call with a skill's name to read its SKILL.md; add the path of one of its files to read that file.

validate_graphql_codeblocks

ChatGPT
Validates GraphQL operations against the Shopify schema to catch hallucinated fields, incorrect types, or invalid syntax BEFORE executing them. Supports the Shopify Admin GraphQL API. Pass each GraphQL operation as a codeblock with raw GraphQL content (NOT markdown-formatted). After validation succeeds, execute the operation with graphql_query (for queries) or graphql_mutation (for mutations). If validation fails, fix the errors and re-validate before executing.

add-to-collection

Claude

bulk-update-product-status

Claude

claim-storefront-preview

Claude
Signal that the user clicked a storefront preview's signup link. Revokes the current shop token (if any) so the next tool call prompts a fresh OAuth for the newly claimed store. Called only by the get-new-store-previews tool's widget — never invoke directly from the model.

create-collection

Claude

create-digital-product

Claude
Create a draft product through Shopify Digital Products. The result includes the product and first variant identifiers used to attach and deliver the digital file. If the merchant is selling access to something already on the web — a Notion template, an online course, a booking page — pass it as 'link' and skip the file upload; the link must be hosted by a provider Digital Products supports, and if it is not, the reply names the ones that are. To set the price and the buyer-facing description, call update-product with productId as its 'id' and variantId in 'variants' — prices are in the shop's own currency, so ask the merchant for the amount rather than guessing one. Do not rename the product through update-product: Digital Products keeps its own copy of the title. This tool does not publish the draft.

create-discount

Claude

create-product

Claude

find-mock-shop-catalogs

Claude
Find ready-made sample catalogs (from mock.shop) that fit the merchant's business, so they can pick one to seed their store with realistic products and collections instead of starting empty. WHEN TO USE: - The merchant has a new or empty store and wants sample products, a starter catalog, demo data, or "something to look at" before adding their own products. - The merchant describes what they sell (or plan to sell) and wants a store populated quickly. WHEN NOT TO USE: - The merchant wants one-off placeholder products rather than a whole catalog — use find-sample-product. - The merchant wants real products to source or resell — this returns sample data, not supplier inventory. - The merchant wants to browse products already in their store — use search-products. INPUT: a short description of the business or what it sells (e.g. "handmade soy candles", "supplies for a new puppy", "streetwear for teens"). Take it from what the merchant said. If they gave no hint at all, ask one question — what do they plan to sell? — then call. OUTPUT: up to limit catalogs (default 3), best match first. Each has a name, short description, categories, collection titles, product and collection counts, currency, and a storefrontUrl the merchant can open to browse it as a live storefront. Present them as a short list with the storefront links and ask the merchant which one they want. Pass the chosen catalog's subdomain to import-mock-shop-catalog to copy it into their store. An empty list means nothing matched well — suggest the merchant describe their business differently.

generate-business-names

Claude
Generate business name ideas for someone starting a Shopify store. WHEN TO USE: - The user wants name ideas for a new business or store. - The user has described a business but has not named it yet. - The user has a name and wants alternatives in the same vein. WHEN NOT TO USE: - The user already knows the name they want and only needs to set it — that is done in the Shopify admin, not here. - The user wants a product name, a slogan, or a tagline rather than a business name. INPUT: a short description of the business in the user's own words — what they sell, who it is for, or the feeling they want ('hand-poured soy candles for dark, woody scents'). Max 255 characters. Pass what the user actually said; do NOT invent a business they have not described. Every name comes back with a signupUrl, the link that acts on it, so present it rather than describing it. Where it goes depends on the user: with no Shopify store connected it opens store signup with the name already filled in; with a store connected it opens the store name setting in that store's Shopify admin, where they save the new name themselves. Either way the tool only hands back a link — it creates and renames nothing. A store name is not exclusive, so the user can take any of these for their store. Nothing here is verified, though — no trademark search, no business registry, no check of whether someone else is already trading under the name — so tell them to check that before building a brand on it.

generate-domain-names

Claude
Suggest available domain names for a Shopify store. Every domain returned has been checked against the domain registry and was available at the time of the call. WHEN TO USE: - The user wants a domain for a business or store name. - The user's preferred domain is taken and they want alternatives. - The user asks whether a domain idea is available. - The user wants to know what a domain costs. - The user wants to buy or register a particular domain. WHEN NOT TO USE: - The user wants to connect or troubleshoot a domain they already own — that is done in the Shopify admin, not here. - The user only wants store-name ideas and does not care whether a domain is available or what it costs. INPUT: a store name, a domain the user has in mind, or a short description of the business. All three work. If the user named a domain, the tool checks that exact domain, checks the same name at other common TLDs, and also returns 3 alternatives. An unusual TLD is fine — keep the one the user said. Pass the domain on its own as the query, or — when it sits inside a sentence — put it in exactDomain. If the user named no domain, put the words the domain should be built from in storeName: a name the user proposed ('volcanic balloon', 'Ember & Oak'), or the subject of what they described ('a domain about hippos, giraffes, and iguanas' → 'hippos giraffes iguanas'). Four words at most, lead-in and connecting words dropped, in the user's own words rather than converted to a domain yourself. The tool compresses them into a domain and checks that the same way; without storeName there is no availability check for a query like that, only suggestions. Only the exact domain checked can come back unavailable. Every other domain returned is available to buy, so do not describe any of them as taken, and do not say which TLDs were checked — an unlisted TLD may have been taken or may not have been quoted, and you cannot tell which. Every domain on offer carries a signupUrl, the one link that buys it, so present it rather than describing it. Where it leads depends on whether a Shopify store is connected to the call, not on whether the user owns one. With a store connected, it opens that domain's purchase page in that store's Shopify admin, so buying it attaches the domain to the store rather than starting a second one; the response says when this applies. Without one, it opens store signup with the domain already selected, even for a user who says they already have a store. Availability is a point-in-time check, not a hold. Tell the user to register a domain they want promptly, and never promise a domain is still available later in the conversation. Prices, where present, are the registry's quote for the first registration term in the stated currency. Renewal is priced separately and is often higher, so present a price as what registering costs today, not as an ongoing rate. A domain can come back without a price; say nothing about its cost rather than guessing, and in particular do not read a missing price as a domain that costs nothing. Every domain here has to be bought. Say a domain is "available" or "unavailable" — never that it is "free", which states a price rather than an availability and states it wrongly.

get-collection

Claude

get-digital-product

Claude
Show the merchant a card for a digital product: its media image, title, price, status, and what the buyer receives. Call this after each step of the digital product flow — after the price is set, after the file is attached, after the media image is added, and after publishing — so the merchant sees the listing as it stands. Every field is read back from Shopify, so the card is current rather than a summary of what was asked for. This only reads. It changes nothing about the product.

get-digital-products-install-status

Claude
Report whether the Digital Products app is installed on the authenticated store. Call this once after the merchant says they have finished the Shopify Admin install flow that open-digital-products-install handed them. Do not poll it.

get-inventory-levels

Claude

get-order

Claude

get-product

Claude

get-shop-info

Claude

get-storefront-generation

Claude
Get the current state of a storefront generation. Used by the widget to poll for preview completion.

graphql_mutation

Claude

graphql_query

Claude

graphql_schema

Claude

import-mock-shop-catalog

Claude
Copy a mock.shop sample catalog's starter set — its first 2 collections and up to 8 products from each (with variants, prices, images), so at most 16 products — into the merchant's connected store, publishing everything to the Online Store. Use it after the merchant picks a catalog from find-mock-shop-catalogs. One call does the whole import. RE-RUNNING IS SAFE AND NEVER OVERWRITES: calling again (after a timeout or partial: true) adds only what is missing — products not yet imported, memberships and publications not yet made. A product already imported from this catalog is left exactly as it is — including any edits the merchant has made since, and including whether it is published — and counted under unchanged; if it is not published, it is listed under unpublished for the merchant to publish or delete in Admin. A product the merchant already has at the same handle from elsewhere is left untouched and reported under skipped. A collection the merchant already has at the same handle is reused when its title matches the catalog's (missing imported products are added to it) and skipped when it does not. Collections are created only with their imported products, so none is ever left empty. INPUT: subdomain from the chosen catalog (e.g. "pets"). Nothing else. OUTPUT: counts of products created/unchanged/skipped and collections created/reused/skipped, and currency. If partial is true Shopify rate-limited the call: wait a few seconds, then call again with the same subdomain. Prices are copied as plain amounts; when currency.mismatch is true tell the merchant prices came from a ${currency.source} catalog and were not converted, so they should review them.

list-customers

Claude

list-orders

Claude

open-digital-products-install

Claude
Get a Shopify Admin install link for Digital Products on the authenticated store. Use this only after the merchant has explicitly asked to install or prepare Digital Products for their store. The app identity is fixed by Shopify; this tool cannot install arbitrary apps and does not install anything silently. Relay the link to the merchant and ask them to come back here once the install is done. They must complete the Shopify Admin install flow before Digital Products connector tools can continue; call get-digital-products-install-status once they say they have.

publish-digital-product

Claude
Take a draft digital product live through Shopify Digital Products, so buyers can purchase and download it. Activates the product and requests its Online Store listing. Refuses to publish a product with nothing attached, so attach the file first with upload-digital-product-file. Digital Products does not report whether the Online Store listing succeeded, so tell the merchant to check the product in their Online Store if buyers cannot find it.

run-analytics-query

Claude

search_collections

Claude

search_docs_chunks

Claude

search_products

Claude

set-inventory

Claude

switch-shop

Claude

test-digital-products-connection

Claude
Verify that the connected store can exchange its Admin token and reach the Digital Products connector. This read-only check returns no credentials or connector data.

update-collection

Claude

update-product

Claude

upload-digital-product-file

Claude
Give the merchant a Shopify Admin link for attaching the downloadable file to a digital product they have already created. Call this after create-digital-product, passing back the product and variant identifiers it returned. This host cannot take a file from the merchant, so the attachment is finished in the Digital Products app rather than here. Relay the link this returns and ask the merchant to report back here once the upload is done; nothing tells this conversation on its own. This does not create products and does not publish anything.

upload-digital-product-media

Claude
Give the merchant a Shopify Admin link for adding a media image to a digital product they have already created. Ask the merchant whether they want a media image first, and only call this if they say yes. A digital product sells perfectly well without one. This host cannot take an image from the merchant, so it is added on the product's page in Shopify Admin rather than here. Relay the link this returns and ask the merchant to report back here once the image is added; nothing tells this conversation on its own. This does not change the price, description, attached file or status, and it does not publish anything.

upload-image

Claude

validate_graphql_codeblocks

Claude

Capabilities

InteractiveWrites

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/shopify"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/shopify)