Summary

Shopify says WebMCP tools are live on Liquid storefronts and Hydrogen’s developer preview, letting compatible browser agents search products, manage carts and take shoppers to checkout. Agent support is currently limited to Chromium-based browsers.

Shopify says WebMCP tools are live on every Liquid storefront and on storefronts built with the Hydrogen developer preview. They give compatible browser-based AI agents structured ways to search a store, inspect products, update a shopper’s cart and move to checkout, rather than relying on simulated clicks. Support for WebMCP agents is currently limited to Chromium-based browsers.

How agents interact with a Shopify store

WebMCP is a proposed web standard in which a website registers tools with the browser. An agent can select a tool and provide structured inputs; the tool returns structured data. Shopify’s documentation describes this as an alternative to an agent reading page code and trying to operate buttons and links on its own.

The tools act on the shopper’s live browser session. Catalog searches draw on the Storefront API, while cart updates use standard storefront actions—the same functions Shopify apps use to change a cart. That means cart changes appear in the session the shopper is viewing. If a store theme has configured a cart-update action to open a cart drawer, for example, an agent’s cart change can trigger that behaviour too.

The available tools cover several stages of shopping. An agent can search products, collections, articles and pages; browse collections; retrieve product details such as variants, prices and stock for option combinations; or select a particular variant. Cart tools can show its contents, add items, change quantities or remove them. If a requested cart change is ambiguous, the update tool returns options for clarification without changing the cart.

Other tools can take the shopper to checkout after checking that the cart is not empty, open order history, or search store policies and FAQs. These tools let an agent act within a storefront, but the shopper’s browser tab remains the place where those actions and navigation occur.

Checkout has a separate set of tools

Shopify’s documentation treats checkout as a separate stage. After an eligible checkout begins, its tools replace the storefront tools; an agent is instructed to refresh the browser’s tool list and use the checkout tools if they are registered. If they are unavailable, the agent should hand the shopper off to complete checkout on the page. The storefront documentation points to a separate Checkout WebMCP reference for reading and updating checkout and placing an order.

This division matters because the tools available to an agent depend on where the shopper is in the purchase journey. Shopify is making product discovery and cart actions available through its storefronts, while checkout has its own browser-tool set. The documented browser compatibility is a practical constraint: shoppers need an agent that supports WebMCP in a Chromium-based browser for these interactions to work.

Sources