Executive summary
- What: Shopify now registers WebMCP tools on every Liquid storefront and on the Hydrogen developer preview, letting a browser-based AI agent search the catalog, change the cart, and move a shopper to checkout.
- Why: Agents no longer read your markup and simulate clicks. Interactions run through a structured tool contract, so they are faster and far less likely to break when the theme changes.
- Who: Shopify Plus teams running Liquid themes today, plus headless teams evaluating the Hydrogen developer preview.
What changed
Your storefront now exposes a tool surface to the browser. WebMCP is a proposed standard, currently limited to Chromium browsers under an origin trial, that lets a page register callable tools with structured inputs and returns. Shopify enabled it by default, with nothing to install.
The catalog tools are search_catalog, browse_store, get_product, and show_variant. Cart tools are get_cart, update_cart, and cancel_cart. Checkout and order tools are proceed_to_checkout and manage_orders. A separate tool, search_shop_policies_and_faqs, answers questions about returns, shipping, and store services from your own content.
The detail that matters most: catalog tools read through the Storefront API, and cart tools call the same standard storefront actions on Shopify.actions that apps already use. An agent's cart change therefore behaves like the shopper's own, so if your theme opens a cart drawer on update, the agent triggers it. Everything happens in the tab the shopper is looking at, against their live session.
Why it matters
Two points deserve attention first. There is no rollout project here: the capability is already on, which shifts the work from enablement to verification. And the reliability of agent-driven sessions stops depending on your markup. A scraping agent breaks when you rename a class or restructure a section; a registered tool contract does not.
Your own content also becomes the answer source. Asked about return windows or delivery timing, search_shop_policies_and_faqs answers from your pages rather than a model's assumption, which matters when terms differ by market. The honest caveat is scope: browser agent support sits inside a Chromium origin trial, so instrument this channel now rather than forecasting demand against it.
Role-specific impact
- Marketers: agent sessions will not produce the same event sequence as a human click path. Confirm how cart updates and checkout entries attribute in your analytics before reading movement in conversion data as a real trend.
- Developers: audit how your theme mutates the cart. If it bypasses the standard storefront actions for bespoke AJAX, agent updates may not trigger your drawer or refresh cart UI state. Headless teams should weigh the Hydrogen developer preview against their roadmap; our view on Hydrogen and Oxygen in enterprise headless commerce covers the trade-offs.
- Store admins: policy and FAQ pages are now machine-read. Thin, stale, or contradictory content stops being a tidiness issue and becomes an answer-quality problem.
Use-case example
Real-world scenario
Consider a Plus merchant selling technical apparel across US and EU markets. A shopper asks a browser agent for a waterproof shell, size medium, under 300 dollars, in stock. The agent calls search_catalog, then get_product to see which combinations are purchasable, then show_variant to land on the right variant, then update_cart.
The measurable difference sits in the variant step. On a catalog of several thousand SKUs where colour and size are separate option sets with partial inventory, a markup-driven agent must infer selector state and regularly picks the wrong SKU or stalls; here the tool returns purchasable combinations directly. Track one number as your baseline: the share of agent-initiated sessions reaching add-to-cart without a wrong-variant correction.
Implementation checklist
- Confirm your theme's cart mutations run through the standard storefront actions rather than custom AJAX.
- Test an agent session in a Chromium browser with the origin trial enabled, against a staging store first.
- Walk the full path: search, product detail, variant selection, cart update, checkout entry.
- Review policy, shipping, and FAQ pages for per-market accuracy, since they now feed direct answers.
- Segment agent-driven sessions in analytics and validate attribution before comparing conversion rates.
- For headless builds, check Hydrogen developer preview status against your roadmap rather than assuming parity with Liquid.
- Brief support and merchandising that a cart can now change without a human click.
FAQ
Q: Do we need to install or configure anything to get these tools?
A: No. They are live on Liquid storefronts and the Hydrogen developer preview by default. Your work is verification, and the highest-value check is whether your theme's cart behaviour runs through the standard storefront actions.
Q: Is this the same as connecting our own agent to Shopify?
A: No. These tools serve an agent the shopper brings into their own browser session. Building your own agent that connects to Shopify directly is a separate path, through Storefront MCP and the agentic commerce documentation.
Resources
WebMCP tools reference on shopify.dev
Need guidance? Talk to Makro.