AI NewsInfrastructureAnnouncement
Cloudflare turned on WebMCP for 100,000 Commerce.com storefronts
Cloudflare and Commerce.com rolled out WebMCP across roughly 100,000 merchant storefronts, so an AI shopping agent can call tool functions like search_products and add_to_cart directly inside the shopper's browser session instead of guessing clicks on the page.
Image: Cloudflare
Why it mattersAn agent that shops by calling named tools on the merchant's own domain, not by parsing the page, removes a layer of guesswork that keeps automated purchases unreliable today, and the merchant does not change code to turn it on.
A shopping agent that reads a merchant's HTML and simulates clicks fails when the layout moves, when a modal pops up, or when a step needs a value the agent never saw. Cloudflare and Commerce.com switched on WebMCP across roughly 100,000 Commerce.com merchant storefronts, so an agent can call named tools inside the shopper's browser session on the merchant's own domain.
Cloudflare says WebMCP is a browser standard that gives a tool interface, built on the Model Context Protocol, to the page a user is already on. The site declares tools like search_products({ query, max_price, size }) and add_to_cart({ product_id }), and an agent on the same page can call them. The agent does not open a separate connection to the merchant's server. The call runs in the shopper's session with the shopper's cookies, so the cart and the checkout stay on the real site.
Zero code for the merchant
Cloudflare says a merchant does not change anything on its own storefront. Cloudflare injects the WebMCP script at the edge for every Commerce.com domain, and the tools map to the catalogue and cart that each store already runs. A merchant that does not want this can turn it off from a Commerce.com dashboard toggle, which writes an edge rule that stops the injection.
Commerce.com is a managed storefront platform, so the single switch covers close to 100,000 shops at once. Cloudflare launched the underlying edge WebMCP implementation in beta in August; this is the first large rollout on it.
Still behind a browser flag today
The headline figure is about reach, not use. WebMCP works today in Chrome behind an experimental flag, so an agent needs the flag set or a preview build to call these tools. Cloudflare says the point of turning it on across every Commerce.com store at once is that the catalogue is ready the moment a shipping browser carries the standard.
Cloudflare also keeps payment data out of the tool surface. The agent can search, add to cart and read totals; checkout, address and card entry stay on the normal merchant pages, under the shopper's control. The agent can hand off to the human, which is the model Cloudflare says every WebMCP tool should follow.
For a team building an agent that is supposed to buy things on the open web, this changes the near-term plan. Clicking a mocked-up DOM has to work on tens of thousands of templates, each of which can change without notice. A tool call returns a typed value or an error, which is the surface agents already handle well. The limit is reach: WebMCP is live on roughly 100,000 stores on one network, not on the whole web, and the agent side still needs a browser that implements the standard.
Source
How Commerce.com and Cloudflare are getting storefronts ready for AI agents, Cloudflare blog.
Background: the Model Context Protocol specification and the WebMCP explainer on GitHub.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
