Shopify

Shopify

The installed shopify command wraps Shopify's official MCP server. It is not the Shopify CLI from npm; the only verbs are the four below. Tool names and schemas come from shopify list-tools, never from memory — other Shopify connectors expose tools this one does not.

shopify status
shopify authorize-url
shopify list-tools
shopify call-tool --name <tool-name> --arguments-json '<JSON object>'

Connecting

1. shopify status. If a store is connected, go straight to work.
2. Otherwise shopify authorize-url and share only the returned connect_url with the user. Nothing else in that response is for them.
3. When they say they're done, shopify status, then call-tool --name get-shop-info to confirm which store is connected.

Before a store is connected, search_docs_chunks (searches https://shopify.dev), validate_graphql_codeblocks, find-mock-shop-catalogs, generate-domain-names, and generate-business-names work. get-storefront-generation is usable only with a generationUUID created by Shopify's storefront-generation widget; claim-storefront-preview is a widget callback and must not be called directly. Every other tool, including catalog import, needs a store. Do not ask someone to connect merely to explore sample catalogs, names, domains, or documentation.

Sample catalogs

When someone is starting a store, offer relevant mock.shop sample catalogs before asking them to connect:

1. Call find-mock-shop-catalogs with what they sell, in their own words. If they have not said, ask that one question first.
2. Present the best matches with their descriptions, product and collection counts, currency, and storefrontUrl. Clearly label each link as the source sample storefront, then ask which catalog they want.
3. Once connected, confirm before calling import-mock-shop-catalog with the selected subdomain.
4. Verify the destination records with search_products and search_collections, then report created, reused, skipped, unpublished, or partial results and any currency mismatch.

An import copies the first two collections and up to eight products from each, at most sixteen products, and publishes newly imported records to the Online Store. Repeating the same import is safe: it fills missing records and memberships without overwriting previously imported products or merchant edits. If Shopify reports partial: true, wait briefly and repeat the same import. These are sample records to edit or replace before launch, not supplier stock.

Users without a store

The same connect_url works for someone who has never used Shopify. Shopify's sign-in page lets them create an account and a new store, then returns them to the connection. Tell them this up front so they don't go create a store separately first. Once connected, offer a first-store sequence and take it one step at a time:

1. get-shop-info to learn the store's name, currency, and plan.
2. Import the sample catalog they selected, or use create-product for their own products (title, description, price, images by URL). Ask what they sell; don't invent a catalogue.
3. create-collection, then add-to-collection to group them.
4. If they track stock, call get-inventory-levels before set-inventory to resolve the inventory item, location, and current quantity.
5. create-discount for a launch promotion, only if they want one.

Business-name and domain results may include signupUrl links for starting a store. Use those for exploration; when the user is ready to connect Muse to their store, share the connector's connect_url instead.

Point them at the Shopify admin (the domain from get-shop-info) for anything this server doesn't cover: themes, checkout, payments, shipping, and connecting or buying domains.