Blog

WebMCP for online stores: what it is, what Shopify and BigCommerce switched on, and what other stores can do

WebMCP for online stores: what it is, its status in November 2026, what Shopify and BigCommerce enabled by default, and what a custom store can build.

By Rokibul Hasan8 min read

  • AI
  • E-commerce
A woman on a sofa talking to her laptop screen and gesturing with one hand.

WebMCP is a proposed web standard that lets a page offer its actions to an AI agent as named tools, so the agent no longer has to read the page and simulate clicks. Until this autumn it was mostly a developer experiment. Then Shopify put it on every Liquid and Hydrogen storefront and checkout, and Commerce.com and Cloudflare switched it on for eligible BigCommerce merchants, in both cases by default.

This post is for store owners and developers who want three answers: what it is, what those platforms actually enabled, and what a WooCommerce or custom store can do. The facts are as of 4 November 2026. The standard is a draft and it moves, so treat every detail as dated.

My own site registers WebMCP tools, described below, so part of this is first-hand. It is a small service site with no cart, so I cannot give you evidence that WebMCP sells anything, and I could find nobody who has published any.

What WebMCP is, in plain terms

A store page already knows how to search products and change a cart. WebMCP lets the page say so, in a form an agent can use: a JavaScript function with a name, a description and a schema for its inputs. An agent working in the shopper's browser can call add_to_cart directly instead of hunting for a button.

The tool runs in the page, in the shopper's own session. It sees the same cart, the same sign-in and the same prices that they do. That is the main difference from the server-side protocols it gets confused with.

WebMCP MCP UCP
Runs In the shopper's open tab On a server Between a platform and the merchant's server
Needs a page open Yes No No
Typical store use Search, cart, guided checkout Reading your own business data Cart and checkout on someone else's surface

The project's README says WebMCP is meant to "complement, not replace" backend protocols such as MCP.

Where WebMCP stands in November 2026

  • Specification. The current draft, dated 2 November 2026, is a Draft Community Group Report. It says it "is not a W3C Standard nor is it on the W3C Standards Track".
  • API name. The draft and the README use document.modelContext.registerTool(). Earlier drafts used navigator.modelContext, so code in the wild often checks for both.
  • Forms. A declarative version using attributes on HTML forms is explored separately and, says the README, "is not part of the specification at this time".
  • Browsers. The repo's implementation status page lists origin trials in Chrome 149 and Edge 150, and support in ChatGPT Desktop. Firefox and Safari have links to standards discussions and no status. No browser ships it as a stable feature.

Chrome's documentation, last updated on 7 October, calls it "under active discussion and subject to change". WebMCP is "primarily designed for local browser workflows with a human in the loop", so it is not a route for background bots. And "clients and browsers must visit a site directly to know if it has callable tools", so it does nothing to help an agent find you.

What I could not confirm: whether Gemini in Chrome calls store tools for ordinary shoppers today. Chrome's page points developers to test extensions and says they are separate from Gemini in Chrome.

What each platform enables

Platform What is on Checkout Off switch
Shopify Every Liquid storefront, and Hydrogen 2026-10 storefronts Agent can place the order once the buyer confirms webMcp: false on Hydrogen; none documented for Liquid
BigCommerce Eligible merchants, through Cloudflare Agent builds the cart; the shopper clicks checkout Opt-out in the Commerce.com dashboard
WooCommerce Nothing in core that I could find; a community plugin exists Plugin does not say agents can pay Remove the plugin
Custom store Whatever you register Your decision Yours

Shopify. Shopify's documentation lists catalogue tools (search_catalog, get_product), cart tools (get_cart, add_to_cart), checkout tools and store information tools such as search_shop_policies_and_faqs. The checkout tools arrived on 28 September 2026, and Shopify says they "don't expose a new API or require merchant configuration". They hand back to the buyer when their input is needed, for 3-D Secure or a blocking UI extension. complete_checkout places the order only after the buyer confirms.

The docs also say agent support is currently limited to Chromium-based browsers. They describe a switch for Hydrogen and none for Liquid, so I would not assume a Liquid store can opt out. My guide to the Shopify Fall '26 Edition shows how this fits with the rest of that release.

BigCommerce. On 21 October 2026, Cloudflare described enabling WebMCP across Commerce.com's storefronts at the edge, with an opt-out for each merchant. Coverage of Commerce.com's announcement quotes it as on by default for eligible merchants, and I could not find how "eligible" is defined. Cloudflare says Commerce.com runs almost 100,000 domains on its network. If a browser has no WebMCP support, the script exits and shoppers notice nothing. The shopper finishes the purchase personally, which Cloudflare says keeps payment details secure.

WooCommerce. The closest thing I found is WebMCP Bridge on WordPress.org: version 1.9.3, more than 700 active installs, one listed contributor and no sign of endorsement by WooCommerce. Treat it as you would any third-party code that touches your cart, and read it before you install it.

Adding WebMCP to a custom store

Start with read-only tools. They answer real questions, carry little risk and teach you what agents ask for. Here is an illustration of one store tool, using the same registration pattern my site uses:

const modelContext = document.modelContext ?? navigator.modelContext;

if (typeof modelContext?.registerTool === "function") {
  modelContext.registerTool({
    name: "get_delivery_estimate",
    description: "Delivery options and dates for one product to one postcode.",
    inputSchema: {
      type: "object",
      properties: { sku: { type: "string" }, postcode: { type: "string" } },
      required: ["sku", "postcode"],
    },
    annotations: { readOnlyHint: true },
    async execute({ sku, postcode }, options) {
      const query = new URLSearchParams({ sku, postcode });
      const response = await fetch(`/api/delivery?${query}`, { signal: options?.signal });
      return response.json();
    },
  });
}

Where the API is missing, nothing runs and the page behaves as normal. The specification requires a secure context, so the page has to be on HTTPS.

A sensible order for a custom store:

  1. Product and policy lookups: search, details, stock, delivery, returns.
  2. Cart changes: add, update and remove, using the same endpoints your own pages call.
  3. A hand-off to checkout: open the checkout page and stop there.

Most stores should stop at step three. An agent-driven payment step on a custom store is a lot of risk for an unmeasured channel.

Designing tools that do not misfire

The specification's security section is useful reading, because several of its examples are about shopping.

  • Name what the tool does. Its example of "ambiguous finalization" is a finalizeCart tool that actually triggers a purchase. An agent may call it just to view the cart. If a tool spends money, the name and description should say so.
  • Mark the risky ones. readOnlyHint says a tool only reads. consequentialHint flags actions that are significant or hard to reverse, so agents can insist on confirmation.
  • Treat hints as hints. The draft says preventing manipulation is "primarily the responsibility of the agent's own security model". Your rules on price, stock and limits belong on your server.
  • Ask for what you need. It warns against tools that gather details such as age or location under the guise of personalised recommendations.
  • Keep secrets out of arguments. Shopify's tools take no authentication tokens, and the shopper's session decides what they can do. Copy that model.
  • Assume customer text is hostile. Reviews and questions can carry prompt injection. untrustedContentHint exists for responses like that.

How devwren.com runs it

My site loads one small script on every page, about 170 lines, registering eight tools. Six only read, and each carries readOnlyHint: search_site, get_pricing, list_services, list_projects, get_contact_details and read_page. Two navigate: open_page, and start_project, which opens the contact form, optionally with a plan filled in. Nothing submits the form or sends a message. The visitor does that.

The lookups read the same build-time files as my read-only MCP server, so the tools can only repeat what the site already publishes. The script is a plain module rather than part of the React app, so tools exist as soon as the HTML has loaded, and an AbortController unregisters them on pagehide.

The site holds no origin trial token, so in ordinary Chrome the script finds no API and does nothing. The tools appear only where the browser or agent already exposes WebMCP. A store that wants ordinary Chrome users to reach its tools during the trial would need to register.

Should you spend money on WebMCP?

On Shopify or BigCommerce, no. Your money is better spent on what the tools return: complete products, accurate stock and clear policies. My guide to AI search optimization covers those levers. I have seen nothing to suggest WebMCP helps you rank.

On a custom store, not yet, and not before Cyber Week. Check your logs for agent traffic first. If you do want to experiment, a handful of read-only tools is a small job that reuses endpoints you already have. That is custom work, quoted from a brief, and the pricing page shows how the published plans work.

FAQ

Is WebMCP the same thing as MCP?

No. MCP connects an AI app to a server and works with no web page open. WebMCP runs in a browser tab, so the agent uses tools the page registers, in the shopper's own session, with the same cart and sign-in. The project describes it as a complement to backend protocols.

Do I need to add WebMCP to my Shopify store?

No. Shopify's documentation says it provides WebMCP tools on every Liquid storefront and on Hydrogen 2026-10 storefronts that load its scripts, and the checkout tools need no merchant configuration. There is nothing to install. Your part is the content those tools return, so keep product data, stock and policies accurate.

Can a browser agent buy from my store without the customer agreeing?

Not on the platforms that document this. On Shopify, complete_checkout places an order only after the buyer confirms, and control returns to the buyer for steps such as 3-D Secure. On BigCommerce, Cloudflare says the shopper clicks checkout personally. On a custom store the answer depends on what you build, so do not offer a tool that pays, and enforce your limits on the server because tool hints are advisory.

If you want WebMCP on a custom store, or want to know whether it is worth it, send me a short brief: your platform, what you would want an agent to be able to do, and what your logs show about agent traffic. You can send it through the contact page, read about the AI agents I build for businesses, or see the wider picture in agentic commerce for online stores.