Shopping agents do not fail because a product page lacks a button. They fail because the page gives them a visual surface and asks them to infer the contract. A theme change, a modal, or a slow script can turn a previously working click path into guesswork.
Cloudflare's write-up with Commerce.com presents WebMCP as the alternative: a browser standard that lets a page expose structured tools such as product search. The agent calls the tool directly instead of hunting through HTML, which can make the interaction faster, cheaper, and easier to reason about.
The fallback is part of the design
The practical details are more interesting than the headline. Cloudflare describes a configurable MCP path because partners do not always host the server at the same URL, and a fallback that exits cleanly when the MCP server or browser support is missing. Human shoppers still get the normal storefront.
An agent-ready page needs a tool contract and a human fallback, not a second fragile interface.
For builders, the early lesson is narrow: expose one useful, permission-aware task with clear inputs and outputs. Keep checkout and irreversible actions visibly user-controlled. A structured tool is an interoperability surface, not permission for an agent to improvise the rest of the transaction.
Cloudflare describes a WebMCP bridge for structured storefront tools, a configurable MCP path, and a fallback that leaves the human storefront unchanged when the agent path is unavailable.
Cloudflare Blog · How Commerce.com and Cloudflare are getting storefronts ready for AI agents ↗
