How Commerce.com and Cloudflare are getting storefronts ready for AI agents

Commerce.com, a commerce platform running close to 100,000 domains on Cloudflare, has turned on Cloudflare's edge implementation of WebMCP across its storefronts, with an opt-out switch for individual merchants. Cloudflare first shipped the edge implementation in August as a beta; enabling it injects a small script at the edge that exposes structured shopping tools to AI agents without site owners editing code or themes. The arrangement was described by Cloudflare AI, with Kristina Pototska, Product Management Director at Commerce.com, explaining the merchant rationale.
WebMCP is a proposed browser standard originating at Google. Rather than reading a page's HTML, guessing which element is a button, clicking and retrying, an agent discovers named tools on the page through an interface the article refers to as document.modelContext. A typical shopping flow becomes a small number of explicit calls, such as search_products with a query, a maximum price and a size, followed by add_to_cart with a product ID. Cloudflare frames the payoff as fewer tokens, faster completion and far greater reliability, since a theme change no longer breaks the interaction. The standard is experimental and in early preview: it sits behind a Chrome flag (chrome://flags/#enable-webmcp-testing), appears in Chrome Origin Trials, in some agentic browsers, and in developer environments such as Cloudflare Kitesurf.
The integration rests on two design choices. WebMCP tools execute inside the shopper's active browser session on the storefront's own domain, so the agent sees the same prices and cart the shopper would, credentials are not handed to a third party, and the visit stays on the merchant's site. Separately, Cloudflare acts as the edge delivery layer in front of Commerce.com's backend MCP server, proxying tool definitions and requests unchanged so merchants keep control of their tool logic. Commerce.com's server-side MCP and WebMCP share the same set of shopping tools: server-side MCP covers agents connecting to a store directly, such as an assistant comparing several shops, while WebMCP covers agents operating in the shopper's browser. In the described flow, the human still completes checkout by clicking, so payment details stay with the shopper.
The practical obstacle was granularity. WebMCP was designed as a single on-or-off switch for a whole domain zone, but Commerce.com hosts thousands of merchant vanity domains on shared zones through Cloudflare for SaaS, so a platform-wide rollout needed per-store control. Rather than a custom allowlist, Cloudflare tied WebMCP to its existing Configuration Rules and custom hostname metadata. Commerce.com enables WebMCP on its main zone and adds an edge rule that checks a metadata flag; when a merchant sets webmcp_opt_out to true in the Commerce.com dashboard, the rule sets webmcp_enabled to false for that storefront. Because evaluation happens at the edge before the page is served, an opted-out store gets no injected script, no remote lookups and no added latency.
Two further details emerged from the real-world deployment. Commerce.com's MCP server lives at /api/mcp rather than the /mcp path the bridge originally assumed, so Cloudflare added a zone-level configurable MCP URL that is passed into the injected module script tag alongside the enabled toolpacks (c2pa and mcp-server-client). And the script fails safe: if a store's MCP server is unreachable or the visitor's browser lacks WebMCP support, it exits and the storefront loads normally, so human shoppers are unaffected. For developers, this is a useful pattern to copy: an edge-injected capability with a metadata-driven kill switch and a no-op fallback keeps a preview feature from becoming an outage or a support burden.
This suggests the broader shift is from agents scraping human interfaces to sites publishing machine-readable affordances. The trade-off is that the standard is young and depends on browser adoption outside the Chrome flags and Origin Trials, so stores get partial coverage for now. Proxying tools through the edge also means the merchant's server becomes the source of truth for catalog and cart behavior, which is good for consistency but puts weight on that server's availability. Cloudflare says it will keep investing as the standard evolves, starting with making a site's tools easier for agents to discover. The two companies will also appear together at Cloudflare Connect in San Francisco on October 21, 2026, in a panel titled Getting your storefront agent ready for peak season, featuring Pototska alongside Justis Blasco of Popmenu, Ross Harvey of Fruugo and Josh Mills of Gopuff.
Why it matters: merchants on shared commerce platforms can now expose agent-friendly tools across an entire estate without per-site work, while individual stores retain an instant opt-out, which lowers the barrier to supporting agentic shopping. For developers, the interesting part is the architecture, edge injection plus hostname metadata and graceful fallback, rather than the specific commerce calls. Teams building storefronts or agent integrations should expect agent traffic to be evaluated on published tools, not clickable pages, though browser support outside early preview channels remains the limiting factor, and that is an inference from the stated availability rather than a confirmed timeline.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Almost 100,000 Commerce.com domains now give AI agents real shopping tools through WebMCP on Cloudflare. Here's how we turned it on across every store at once, while keeping each merchant in control.