Commerce.com has turned on WebMCP for almost 100,000 of its domains, working with Cloudflare, according to a Cloudflare blog post. The aim is to let AI agents shop a store through defined tools rather than by reading the page and guessing which button to press.
What changes for agents
Most shopping agents today work from a site's HTML. They look at the page, guess what each control does, click, and retry on failure. Cloudflare says this is slow, token-hungry and fragile, and that even a theme change can break it.
WebMCP is a Google-backed browser standard that gives a page structured tools, such as search_products. On an enabled Commerce.com store, an agent finds the tools in the browser and calls them directly. In the source's example, a request for a waterproof trail running shoe under $140 in size 10 becomes two calls: search_products, then add_to_cart.
The tools run inside the shopper's own browser session on the store's domain. The agent therefore sees the same prices and cart as the shopper, and no credentials go to a third party. The shopper clicks checkout personally, so payment details stay with them.
How the rollout works
Cloudflare launched edge WebMCP in beta in August. When it is enabled, Cloudflare injects a small script at the edge, and the site owner writes no code. Commerce.com's tool logic lives in its backend MCP server, and Cloudflare proxies tool definitions and actions unchanged. Commerce.com says WebMCP works alongside its server-side MCP, which serves agents that connect to a store directly.
Two changes were needed for a platform of this size:
- Per-merchant opt-out. WebMCP was designed as one switch for a whole zone. Commerce.com turned it on for its main zone and added a Configuration Rule that checks custom hostname metadata. A merchant who flips the opt-out in the Commerce.com dashboard is skipped at the edge. According to Cloudflare, an opted-out store gets no extra latency, no remote lookup and no injected script.
- Custom MCP path. The bridge assumed each MCP server sat at /mcp, while Commerce.com's is at /api/mcp. Cloudflare added a zone-level setting for the URL.
If a store's MCP server is offline or the visitor's browser lacks WebMCP support, the script exits and the storefront loads as normal.
Limits
WebMCP is an experimental, proposed standard in early preview. It is available behind a Chrome flag, in Chrome Origin Trials, in some agentic browsers and in developer environments such as Cloudflare Kitesurf. The source gives no figures on how many shoppers or agents use the tools. Cloudflare says it will next work on helping agents discover a site's tools more easily.