Commerce.com turns on WebMCP across its storefronts

Commerce.com is using Cloudflare to switch on WebMCP across almost 100,000 storefront domains, Cloudflare said in a blog post. WebMCP is an experimental browser standard from Google that lets a web page give AI agents structured tools, such as search_products, so they don't have to read a page's HTML and guess which button does what.

Cloudflare released its edge implementation of WebMCP in beta in August. When it is enabled, Cloudflare adds a small script to pages at the edge, so the tools work without site owners writing any code. For Commerce.com, Cloudflare's mcp-server-client toolpack passes tool definitions and requests from Commerce.com's backend MCP server to the shopper's browser without changing them.

The tools run inside the shopper's own browser session on the merchant's domain. The agent sees the same prices and cart as the shopper, and no credentials go to a third party. In Cloudflare's example, an agent finds a shoe and adds it to the cart with two calls: search_products and add_to_cart. The shopper still clicks checkout themselves.

WebMCP was built as a single on/off switch for a whole domain zone, so it couldn't be turned on per store. To get around this, the companies used Cloudflare Configuration Rules together with custom hostname metadata. Commerce.com turns WebMCP on for its main zone, and merchants can opt out from their dashboard. According to Cloudflare, the rule is checked at the edge, so an opted-out store gets no added latency and no injected script.

Kristina Pototska, product management director at Commerce.com, said WebMCP works alongside the company's server-side MCP and uses the same set of shopping tools.

WebMCP is still in early preview. It is available behind Chrome flags, in Chrome Origin Trials, in some agentic browsers and in developer environments such as Cloudflare Kitesurf.