WebMCP for Shopify

This is the guide that changed the most in 2026. On August 5, 2026, Shopify shipped WebMCP natively on every Liquid storefront (and the Hydrogen developer preview) — zero config. If you're on Shopify, agents can already search your catalog, manage the cart, look up orders, read policies, and reach checkout without you writing a line of code. So the job changed: it's no longer "how do I add WebMCP to Shopify," it's "what do I get for free, what do I still have to fix, and where do I extend it."

What Shopify now does for you automatically

Per Shopify's WebMCP docs, every Liquid storefront registers a standard tool set in the shopper's browser session:

• Catalog search — agents query your products by natural language.
• Cart management — add, update, and remove items in the shopper's live cart.
• Checkout — hand the shopper to checkout to complete payment themselves.
• Order lookup — status for the signed-in customer.
• Policy search — returns, shipping, and store policies.

It runs in the shopper's authenticated session, in Chromium browsers via the Chrome origin trial, with the human completing payment — the security model working as intended. Shopify co-authors the spec with Google and Microsoft, so this tool set will grow.

Step 1 — Confirm it's actually working on your store

"Native and automatic" still deserves a check — themes, apps, and aggressive JS optimization can interfere. Install Google's Model Context Tool Inspector extension, open your storefront in Chrome, and confirm the Shopify tools appear with valid schemas. Then run our free scan — your capabilities category should already pass without any work from you.

Step 2 — Fix the gaps Shopify's tools don't cover

Native tools make your store operable. They don't make it understood — and an agent that can act but can't comprehend your catalog still recommends a competitor. This is where most Shopify stores lose, and none of it is automatic:

• Product structured data: complete Product JSON-LD with offers.price and availability on every product — many themes emit partial or missing schema.
• llms.txt: publish /llms.txt mapping your collections, policies, and key pages so agents and AI search understand what you sell.
• AI-crawler policy: Shopify's default robots.txt doesn't make deliberate decisions about GPTBot, ClaudeBot, Google-Extended, or PerplexityBot — decide which agentic crawlers you want.
• LocalBusiness schema if you have physical locations, and accurate hours.

Step 3 — Extend WebMCP for custom, headless, or non-cart flows

The native tools cover the standard commerce path. You still register your own tools when you have functionality Shopify doesn't ship, or a storefront it doesn't fully auto-instrument:

• Hydrogen / headless (React) storefronts: the developer preview covers the basics, but custom React routes need lifecycle-aware registration — see our React/Next.js guide for the hook pattern.
• Non-cart actions: subscription management, booking or appointment flows, quote requests, size finders, loyalty lookups — none are in the native set.
• Custom apps & metafields: expose store-specific data an agent would ask for but Shopify's generic tools don't surface.

Register additional tools with a theme-app-extension or an assets/ script:

const mc = document.modelContext ?? navigator.modelContext;
if (mc) {
  mc.registerTool({
    name: "check_size_availability",
    description: "Check which sizes of a product are in stock. Use before recommending a purchase.",
    inputSchema: { type: "object",
      properties: { productHandle: { type: "string" } }, required: ["productHandle"] },
    annotations: { readOnlyHint: true },
    async execute({ productHandle }) {
      const p = await (await fetch(`/products/${productHandle}.js`)).json();
      return p.variants
        .filter(v => v.available)
        .map(v => ({ size: v.title, price: v.price / 100 }));
    }
  });
}

Don't re-register what Shopify already provides — duplicate search_products or add_to_cart tools confuse agents. Add only what's missing.

The bottom line for Shopify merchants

The capability layer is handled for you — a genuine head start most platforms don't have. Your competitive edge is now everything around it: complete structured data, a clean llms.txt, deliberate crawler policy, and custom tools for the flows that make your store different. Our deep audit crawls your live store, confirms which native tools are firing, and blueprints exactly which custom tools and comprehension fixes will move your numbers — or start with the free scan.