The News, Explained
On October 21, 2026, Cloudflare described its work with Commerce.com to bring WebMCP shopping tools to storefronts. WebMCP lets a webpage advertise defined functions to an AI agent: software that carries out tasks requested by a user. Here, those functions include product search, cart management and a handoff to checkout. Source
Calling store functions instead of finding buttons
An agent using an ordinary shopping page has to locate inputs, product options and cart buttons. The integration described by Cloudflare lets it call the store’s search and cart functions directly. Locating a button on a screen and submitting product requirements to a defined tool become distinct tasks. Source Source
MCP is a shared protocol for AI programs to discover and call external functions. A store’s MCP server supplies commerce functions; WebMCP makes them available inside the browser where a shopper has opened that store. Cloudflare delivers a small bridge script and proxies the tool definitions and requests controlled by Commerce.com’s backend server. Source Source Source
These tools run within the shopper’s active browser session on the storefront. A session carries the current visit’s state, such as sign-in and a cart. Cloudflare says this gives the agent the same prices and cart as the shopper. Source
Cart assistance, followed by a human purchase decision
As a hypothetical example, a shopper could give an agent a preferred bag color and budget, then have it search and add a matching item through the store’s tools. In the Commerce.com flow described in the announcement, the shopper personally clicks checkout at the final purchase stage. Source
The division of work is therefore between searching and preparing a cart, and making the final purchase decision. The visit and cart remain with the merchant while its tools are used, and the human takes the action that proceeds to checkout. Source
Browser previews and individual store choices
WebMCP remains an experimental proposed browser standard in early preview. The announcement lists environments such as experimental Chrome settings, Origin Trials and some agentic browsers. Origin Trials let websites test experimental browser features under limited conditions. Actual use depends on support across the agent, browser and storefront. Source Source
Commerce.com enables WebMCP across its platform while allowing individual merchants to opt out. A merchant’s dashboard choice causes Cloudflare to skip the bridge for that storefront. Cloudflare also says that if a browser lacks support or the store’s MCP server is offline, the bridge exits and the ordinary storefront loads normally. Source
Opening the store’s backend functions has its own conditions. BigCommerce’s MCP documentation requires the store owner to enable Storefront MCP and accept the terms. Additional business-to-business tools depend on B2B Edition and the signed-in buyer’s permissions. Platform delivery settings and the functions authorized by the store therefore need to be considered together. Source
OYOPICK’s Take
The useful feature of this design is a fairly clear division of responsibility. It combines help with finding products and preparing a cart with a human’s final purchase decision. If an agent can use store tools while preserving the existing cart and price context, the workflow could become easier for shoppers to follow.
For that promise to become practical convenience, shoppers need to see which tools a store exposes, what the agent added and when their own checkout action is required. Merchant opt-outs and a path back to ordinary pages support that choice. As availability expands, we would assess accuracy in selecting products and options alongside the clarity of the purchase process.