Cloudflare and Commerce.com bring WebMCP agent tools to nearly 100,000 storefronts

Cloudflare and the commerce platform Commerce.com have switched on agent-ready tooling across almost 100,000 storefront domains at once, using an edge implementation of the experimental WebMCP browser standard. According to the Cloudflare blog, the rollout gives AI shopping agents structured tools such as product search and add-to-cart on participating stores, replacing the guesswork of navigating pages designed for humans.

The problem with agents that shop like humans

Most shopping agents today work from a site's HTML: they inspect the page, infer which control does what, click, and retry when they guess wrong. As Cloudflare explains, this is slow, consumes large numbers of tokens, and can break after something as minor as a theme update. Agents also routinely run into cookie banners, variant drop-downs and bot challenges that assume a human visitor.

What WebMCP provides

WebMCP is a proposed browser standard from Google that exposes structured tools on a page, such as a search_products call with query, price and size parameters, instead of forcing agents to simulate clicks. It is still in early preview, reachable behind an experimental Chrome flag, through Chrome Origin Trials, in some agentic browsers, and in developer environments like Cloudflare's Kitesurf.

Cloudflare shipped an edge implementation of the standard in beta in August. When enabled, Cloudflare injects a small script at the edge that makes a site's tools available to agents automatically, with no code changes required from the site owner.

In the shopping flow Cloudflare describes, an agent asked to find a waterproof trail running shoe under $140 in size 10 detects the store's tools on document.modelContext and issues two calls: search_products and add_to_cart. Because the agent operates inside the shopper's active browser session on the store's own domain, the cart updates in real time, the agent sees the same prices the shopper sees, and no credentials pass to a third party. When it is time to buy, the shopper completes checkout manually, keeping payment details under their control.

The engineering behind a 100,000-site rollout

WebMCP was originally designed as an all-or-nothing switch for an entire domain zone. Commerce.com, however, hosts thousands of merchant vanity domains on shared zones through Cloudflare for SaaS, so a platform-wide rollout needed per-merchant control.

The fix hooks WebMCP into Cloudflare's existing Configuration Rules and custom hostname metadata. Commerce.com enables WebMCP for its main zone, and an edge rule checks merchant metadata on each request: if a merchant flips an opt-out switch in their Commerce.com dashboard, Cloudflare bypasses WebMCP for that storefront. Because the rule is evaluated at the edge before the page is served, opted-out stores get no added latency, no remote lookups and no injected scripts.

Working with a real partner also surfaced practical gaps. The edge bridge originally expected each site's MCP server at the path /mcp, while Commerce.com's server lives at /api/mcp, so Cloudflare added a zone-level setting for a custom MCP URL that gets passed into the injected script tag. And if a store's MCP server is offline or the visitor's browser lacks WebMCP support, the script exits and the storefront loads normally for human shoppers.

Commerce.com runs the browser-based tools alongside a server-side MCP server, which serves agents that connect to a store directly rather than through a shopper's browser. Both expose the same set of shopping tools, so merchants manage a single tool implementation rather than two.

Kristina Pototska, product management director at Commerce.com, said merchants keep asking how to keep up with agentic shopping: they want their store to appear when a shopper asks an agent to find something, to keep the customer relationship and control of checkout, and to do it without rebuilding their site. Cloudflare says it will keep investing in WebMCP as the standard evolves, starting with making a site's tools easier for agents to discover.

Why it matters

This is one of the first large-scale deployments of infrastructure built for agent commerce rather than adapted from human-facing pages. The architecture keeps the shopper in control of payment, keeps merchants in charge of their tool definitions and checkout flow, and offers a reusable pattern for other SaaS platforms: platform-wide enablement with per-tenant opt-outs resolved at the edge. The underlying standard is still experimental and its details may change, but with nearly 100,000 storefronts now exposing agent tools, both merchants and agent builders have a working reference for what agentic shopping infrastructure looks like.