Shop MCP is Shopify's new hosted server that lets any AI agent search the Shopify Catalog, build a cart and pay with Shop Pay through one connection, and it changes where a merchant's product page actually gets read. Shopify announced it on October 13, 2026. Until now, an agent that wanted to sell a Shopify product had two choices: talk to each store's own catalog endpoint, or find the product in the global catalog and push the shopper back to the store to pay. Shop MCP removes the second hop. For brands that spent real money on a storefront, that is worth thinking through before the agent traffic shows up.
What Shop MCP does
Shop MCP is a single MCP server at mcp.shop.com that covers search, product details, carts, checkout and order lookup across Shopify stores. The Shopify developer changelog lists the main tools: search_catalog, lookup_catalog and get_product for discovery, cart and checkout creation at the store that sells the item, complete_checkout once the shopper approves the total and payment method, and search_orders for tracking. Shopify puts the reach at over 1 billion products, and search needs no API key.
Sign-in is optional. Anonymous agents can still build carts and checkouts, but a shopper who signs in with Shop brings saved addresses and Shop Pay, which is what lets the agent finish the purchase without opening the merchant's site. Orders land in the merchant's admin like any other order. Two limits stand out: there are no webhooks at launch, so agents must poll get_checkout for status, and existing Catalog API integrations are untouched.
Shop MCP vs Storefront Catalog MCP, compared
Shop MCP is a buyer-side tool that spans every Shopify merchant, while Storefront Catalog MCP is a store-side endpoint that only ever answers for one shop. Shopify's catalog documentation draws the line clearly, and four differences matter for a brand.
Scope. Storefront Catalog lives at /api/ucp/mcp on the store's own domain and returns only that store's products. The global side returns results clustered by Universal Product ID, with offers from several merchants grouped under one product.
Who owns the moment of choice. On a store endpoint, the merchant's catalog is the whole universe. On Shop MCP, the agent compares your offer with every other seller of a similar item, then picks. Your hero video, your size guide and your editorial copy are not in that comparison unless they made it into structured product data.
Payment. Shop MCP can complete checkout with Shop Pay for a signed-in buyer. Without that sign-in, the agent hands back the store's checkout link, which is slower but keeps the buyer on your brand.
Identity. Both catalog endpoints expect an agent profile rather than an API key, so the cost of building an agent that queries your store is close to zero. Expect more of them, not fewer.
Why Shop MCP matters for premium brands
Shop MCP turns product data into the storefront for any shopper who buys through an agent. That is the uncomfortable part for premium merchants. A brand that sells through its own store and through three authorised retailers now appears as one clustered product with four offers, and the agent's choice will lean on price, stock, delivery and a few attributes. Brand experience does not travel through a JSON response.
It also widens the gap between what a buyer sees on the site and what an agent reads. Shopify's own skill file for Shop MCP tells agents to filter on Size, Color and Target gender, to accept GTINs and UPCs in lookups, and to treat merchant text as data rather than instructions. A store with inconsistent option names ("Colour" on one product, "Shade" on the next) or missing barcodes is harder to match, and harder to match means less often chosen.
Pricing signals are moving the same way. Since October 5, 2026, the catalog returns a variant's compare-at price as list_price, according to a separate changelog entry, provided the merchant shares it through Catalog Mapping and shows it in the buyer's region. An agent can now say "marked down 30%" on your behalf. Brands that use compare-at as an MSRP reference rather than a real markdown should check that setting today.
For headless builds, the store-scoped endpoint is part of the job now. We covered how the agent routes split between browser and server in our WebMCP checkout comparison and how cart tools moved in the UCP Cart MCP migration. Shop MCP is the cross-merchant layer above both.
What we would do this quarter
Treat structured product data as a design surface and audit it before agent orders become a measurable channel. On our Shopify Plus and Magento Hyvä builds, that work comes in four parts.
First, run the search yourself. Shopify ships a shop CLI that calls the same server, so a merchandiser can type the queries their customers use and see which store wins, at what price and with what stock. It takes an afternoon and it is the clearest picture of agent visibility you will get this year.
Second, normalise options and identifiers. Use one option name per attribute across the catalog, fill GTIN or barcode fields on every variant that has one, and keep variant titles literal. This is boring work with a direct effect on match rate.
Third, decide on compare-at. If your compare-at field holds an MSRP, turn off sharing in Catalog Mapping so agents do not present it as a discount. If it holds genuine markdowns, leave it on.
Fourth, plan for orders you did not see coming. Agent orders arrive in admin with no new webhook to flag them, so tag and report on them through order attribution and sales channel data, and check that post-purchase flows (welcome email, loyalty enrolment, review requests) still fire for a customer who never visited the site. If the brand needs its own assistant rather than relying on someone else's, that belongs in an AI-native interface project, built on the store-scoped endpoint.
Magento merchants are not in Shopify Catalog at all, which is neither good nor bad yet. UCP is an open specification, so the useful move for a Hyvä store is to keep product feeds clean and watch whether other platforms adopt the same catalog shape. Shopify's own docs mention a Universal Cart in early access that spans merchants on and off Shopify, which suggests the cross-platform layer is coming.