Commerce.com Switches On WebMCP Across Its Stores So AI Agents Can Shop Without Clicking

On 21 October 2026 Cloudflare described how it helped Commerce.com get its storefronts ready for AI agents. The mechanism is WebMCP, a browser standard from Google that gives agents structured tools on a web page, such as search_products, so they do not have to click through the HTML.

Commerce.com runs almost 100,000 domains on Cloudflare, and it enabled WebMCP across its stores in one go. Cloudflare injects a script at the edge, so merchants write no code. An edge rule checks a per-merchant metadata flag, and if a merchant opts out, WebMCP is bypassed for that storefront with no extra latency. A zone-level setting can point the script at a non-standard MCP path, and Commerce.com uses /api/mcp. If the MCP server is offline or the browser lacks WebMCP support, the page simply loads as normal.

For shoppers, an agent can call store tools to search products and add items to a cart. Those tools run in the shopper's active browser session on the merchant's own domain, so the agent sees the same prices and cart. The shopper still completes checkout manually, which keeps payment details with them and the customer relationship with the merchant.

The caveats are significant. WebMCP is experimental. It is available behind Chrome flags, in Chrome Origin Trials, in some agentic browsers and in developer environments such as Cloudflare Kitesurf. Cloudflare launched its edge implementation in beta in August.

For web teams building ecommerce sites, the lesson is about structure. An agent-friendly store needs clear product data, stable search and a cart that behaves predictably, and those are the same things human customers have always wanted.

We would treat WebMCP as something to prototype on a staging site, not something to promise a client this quarter. Prototyping now means we understand the shape of the thing when clients start asking, which they will.