Cloudflare Brings Nearly 100,000 Shops Into WebMCP So AI Agents Stop Guessing at Buttons
Shopping agents typically read a page's HTML, guess what each button does, and break even when a store changes its theme. WebMCP is an experimental browser standard from Google that lets a page hand agents a ready-made set of tools, such as search_products. Cloudflare and Commerce.com switched it on for nearly 100,000 store domains at once, without requiring any code changes. Merchants get into agents' answers without rebuilding their sites.
AI-processed from Cloudflare AI Blog; edited by Hamidun News
AI models write code and pass exams, yet buying a pair of sneakers in an online store is still hard for them. The reason is that websites were built for people. Most shopping agents today work with HTML: they look at the page, guess which button does what, click, and try again if they got it wrong.
This is slow, burns a lot of tokens, and breaks over the smallest change, such as a switch of visual theme. WebMCP offers a way out. It is an experimental browser standard from Google in which the page itself tells the agent which ready-made tools are available, for example search_products ("find products").
Cloudflare and the Commerce.com platform enabled this standard at once for nearly 100,000 store domains, and owners did not have to change a single line of code.
What WebMCP is and why a store needs it
An agent no longer has to hunt for buttons: it calls the required function directly. Purchases become faster, cheaper in tokens, and more stable, because a change to the page template does not break the tool call.
The standard is still at an early stage. It can be enabled through an experimental Chrome flag (chrome://flags/#enable-webmcp-testing), through Chrome Origin Trials, in some agentic browsers, and in Cloudflare's developer environment Kitesurf. In August, Cloudflare launched a beta of its WebMCP implementation at the network edge, meaning on its own servers between the site and the visitor. When it is enabled, Cloudflare injects a small script into the page, and the tools appear automatically, without a single line of code from the site owner.
Commerce.com already keeps its nearly 100,000 domains behind Cloudflare, so it asked: can this be enabled for all stores at once? Product director Kristina Potocka explains the motivation: merchants want to appear in agents' answers, keep the customer and control over the checkout, and avoid rebuilding their sites.
What this looks like for the shopper
For example, you ask an agent to find waterproof trail running shoes under $140, size 10, and add them to your cart. Without WebMCP, the agent simulates clicks. It gets blocked by cookie banners, confuses variant dropdowns, and anti-bot checks take it for a bot.
With WebMCP, the agent finds the store's tools in document.modelContext and makes two clean calls: search_products with the query, price, and size, then add_to_cart with the product ID. The agent works inside your active browser session on the store's domain, so it sees the same prices and the same cart, and the cart updates in real time. Payment data is not passed to third parties. The person presses the checkout button, so the final step stays under their control.
WebMCP does not replace Commerce.com's server-side MCP; it works alongside it. The server-side version is for agents that connect to a store directly, such as an assistant comparing several sites. WebMCP is for agents inside the shopper's browser. The toolset is the same in both cases, so merchants do not have to choose between or maintain two separate sets.
What had to be reworked
The first problem: WebMCP was designed as a single switch for an entire domain zone. Commerce.com hosts thousands of customer store domains on shared zones through Cloudflare for SaaS, and each merchant needs the option to opt out. Instead of a complicated allowlist of domains, engineers used mechanisms that already existed: configuration rules and hostname metadata. Commerce.com enables WebMCP for the main zone and adds a rule that checks a webmcp_opt_out flag. If a merchant has enabled opt-out in the dashboard, Cloudflare skips WebMCP for that store. The rule fires at the network edge before the page is served, so an opted-out store has no added latency, no external requests, and no injected script.
The second problem: the mcp-server-client bridge looked for the MCP server at /mcp, but Commerce.com's lives at /api/mcp. So a zone-level setting with a custom MCP address was added, passed to the injected script through the data-mcp-url attribute. In addition, if the MCP server is unavailable or the browser does not support WebMCP, the script simply exits, and the store loads as usual.
What this means in practice
For platform owners and merchants, the takeaway is simple: preparing a site for agents can be done at the infrastructure level rather than by rewriting templates. There are caveats. The standard is experimental, not available to all users, and the timeline for mass adoption is unknown. The material includes no figures on conversion growth or token savings, so the gains are so far described only qualitatively. Developers building agents should watch WebMCP as a way to move away from fragile "clicking through HTML." Cloudflare plans to make it easier for agents to discover a site's tools next.
- Nov 21, 2026A swimming team captain handed ChatGPT three scheduled tasks and cut her routine work by a multiple
- Nov 21, 2026MIRA Neural Network Renders Rocket League at 20 FPS, but Ping Hits 460 ms
- Nov 21, 2026Google built a closed copy of the internet with fake banks to train Chrome's AI agents
- Nov 21, 2026MLPerf Training Adds Nvidia Rubin and TPU Ironwood in First Appearance: 153 Systems
Key Questions Answered
What WebMCP is and why a store needs it?
An agent no longer has to hunt for buttons: it calls the required function directly. Purchases become faster, cheaper in tokens, and more stable, because a change to the page template does not break the tool call. The standard is still at an early stage. It can be enabled through an experimental Chrome flag (chrome://flags/#enable-webmcp-testing), through Chrome Origin Trials, in some agentic browsers, and in Cloudflare's developer environment Kitesurf.
What this looks like for the shopper?
For example, you ask an agent to find waterproof trail running shoes under $140, size 10, and add them to your cart. Without WebMCP, the agent simulates clicks. It gets blocked by cookie banners, confuses variant dropdowns, and anti-bot checks take it for a bot. With WebMCP, the agent finds the store's tools in document.modelContext and makes two clean calls: search_products with the query, price, and size, then add_to_cart with the product ID.
What had to be reworked?
The first problem: WebMCP was designed as a single switch for an entire domain zone. Commerce.com hosts thousands of customer store domains on shared zones through Cloudflare for SaaS, and each merchant needs the option to opt out. Instead of a complicated allowlist of domains, engineers used mechanisms that already existed: configuration rules and hostname metadata. Commerce.com enables WebMCP for the main zone and adds a rule that checks a webmcp_opt_out flag.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.