Shopify

SummaryCopy Anchor Link

Shopify has shipped much of the agentic-commerce stack described elsewhere in this section as platform features rather than things a merchant builds by hand. If you sell through Shopify, much of your work is confirming what is switched on and keeping the data behind it accurate - not implementing UCP or a checkout protocol yourself. Verify every item here against shopify.dev before depending on it; Shopify ships changes on a rolling changelog, not a fixed release cycle.

• WebMCP tools and the storefront cart and checkout APIs need no merchant setup - nothing to install
• Catalog discoverability, Agentic Storefront enablement, and native checkout are three separate things
• Storefronts publish their UCP capabilities at /.well-known/ucp; an agent negotiates through its own agent profile. A merchant still configures order webhooks
• Several MCP servers cover catalog, cart, checkout, orders, and shopping - each with a different job
• Checkout Kit and the product-page audit are the two pieces worth checking by hand

UCP supportCopy Anchor Link

Shopify storefronts support UCP 2026-08-25 as of 2026-09-04, and the UCP version is still 2026-08-25, but the platform's capabilities have grown since: buyer consent (dev.ucp.shopping.buyer_consent, 2026-10-16) on cart and checkout, and optional location search and lookup (2026-10-22). UCP capability is delivered through Shopify's MCP servers and Catalog endpoints (below) rather than a separate integration - storefronts publish their capabilities at /.well-known/ucp, an agent negotiates extensions through its own agent profile (hosted at a URL it controls and referenced on every request), and Shopify's platform handles catalog, cart, and checkout behind it.

MCP serversCopy Anchor Link

Shopify exposes commerce as MCP tools across several servers, each scoped to a different job (see the agents docs for the current map):

• Global Catalog MCP - product discovery across Shopify merchants at https://catalog.shopify.com/api/ucp/mcp (see the migration notice above).
• Storefront Catalog - the same discovery scoped to a single merchant's storefront.
• Cart MCP - builds and iterates on carts with line items, localization, and buyer context.
• Checkout MCP - converts a cart into a checkout and completes purchases for trusted agents.
• Order MCP - post-purchase order state, via a get_order tool.
• Shop MCP (2026-10-13) - at https://mcp.shop.com: Catalog search without an API key, carts and checkout, Shop Pay checkout for a signed-in shopper after they confirm, and search_orders. It has no webhooks at launch, so poll get_checkout.

Shopify's Dev MCP and AI Toolkit are separate development tooling: documentation and guidance for coding tools like Claude Code and Cursor, with no live store data. Access tiers are trust-based: higher tiers unlock direct checkout completion rather than discovery-only access.

Catalog API media-type filterCopy Anchor Link

Shopify's Catalog API added a media-type filter on 2026-09-15, letting a caller narrow catalog search results by media format rather than returning every asset type for a match. Since then it also returns eligible compare-at prices as list_price (2026-10-09, minor-unit price objects), and a US-only beta (2026-10-27) can return brands that don't sell on Shopify, for discovery only (eligible.native_checkout=false).

WebMCP for Liquid and HydrogenCopy Anchor Link

Shopify shipped WebMCP support for Liquid and Hydrogen storefronts on 2026-08-05. WebMCP is the browser-native draft that lets a page register tools directly with an in-tab agent; Shopify's implementation exposes catalogue tools (search_catalog, browse_store, get_product, show_variant) reading product, collection, and search data through the Storefront API, plus cart tools (get_cart, update_cart, cancel_cart) calling standard storefront actions, and shop-policy/FAQ lookup. On 2026-09-28 WebMCP extended into checkout with navigate_to_storefront, get_checkout, update_checkout, and complete_checkout; the last submits the order only after the buyer confirms, and control passes back to the buyer for 3DS or blocking UI extensions. There is nothing to install or configure - the tools are live on every Liquid storefront and on Hydrogen (the new Hydrogen 2026-10 is generally available as of 2026-10-14) in browsers that support WebMCP, without merchant action. This is the mechanism behind an agent browsing your store in its own tab, distinct from the server-side MCP servers above which serve remote agent clients.

Checkout Kit and agentic checkoutCopy Anchor Link

Checkout Kit is an open-source SDK, the successor to Checkout Sheet Kit, for embedding Shopify checkout - the same checkout buyers see on the web, with store branding, checkout UI extensions, and Shopify Functions - inside any surface: iOS (Swift 5.7+), Android (Java 11, SDK 23+), React Native (0.70+), and web (Safari 16.4+, modern Chrome/Firefox). It builds on the Embedded Checkout Protocol (ECP): the SDK handles the ec.ready/ec.start/ec.complete lifecycle, capability negotiation, and recovery over JSON-RPC 2.0, so an integrator passes a checkoutUrl from cart creation and handles completion, failure, and cancellation callbacks rather than implementing ECP directly.

For agentic checkout specifically: an agent using Shopify's MCP servers can take a shopper from discovery to purchase - search, selection, and checkout - inside the agent's own surface. When a checkout step needs a buyer action that isn't supported over MCP (3DS challenges, certain payment methods), the agent falls back to opening web checkout in a browser or presenting it through Checkout Kit or ECP directly for a native, embedded experience rather than failing the flow.

Product-page auditCopy Anchor Link

Shopify's agentic-readiness product-page audit scans a product URL and checks the structured data, real-time pricing accuracy, and trust signals an AI shopping agent would read - the same checks described in Product Data. Shopify frames this as informational rather than a guarantee: it states explicitly that passing signals help agents discover, evaluate, and recommend a product but do not guarantee it will be surfaced. Keep three things apart: Catalog discoverability (a product is in Shopify Catalog and can be found), Agentic Storefront enablement ("Agentic Storefronts" is Shopify's branded feature for surfacing products inside ChatGPT, Gemini, and similar chat surfaces, for eligible stores), and native checkout. Being found does not make a product eligible for native checkout - external-brand products in the Catalog beta always have eligible.native_checkout=false. Confirm each in your own setup rather than assuming one implies the others.

What a merchant must configure vs what arrives automaticallyCopy Anchor Link

Provided by the platform: product catalog structuring and Catalog API access, the storefront's UCP capabilities at /.well-known/ucp, WebMCP tools on Liquid and Hydrogen, and cart and checkout APIs for authenticated agents. Agentic Storefront enablement and native checkout depend on store eligibility and the agent's access tier.

A merchant must configure: order webhooks so an external system can track fulfilment, refunds, and returns (see Orders and After Purchase), and - as with any storefront - accurate product data, return policy, and pricing at the source, since none of the automatic surfaces above fix a wrong price or a missing return policy for you.

Related PagesCopy Anchor Link

• Agentic Commerce - the five-layer overview
• Product Data - what the structured-data and feed layer needs, platform-agnostic
• Checkout Protocols - UCP at the protocol level
• Orders and After Purchase - order webhooks and post-purchase operations
• WebMCP - the underlying browser standard