Almost 100,000 online stores can now hand AI agents a proper set of shopping tools instead of making them click around like a confused tourist. On 21 October 2026, Cloudflare and Commerce.com (the company formerly called BigCommerce) said they had switched on WebMCP across Commerce.com’s storefronts in a single move, and every merchant can still opt out.
Key takeaways
- WebMCP is an experimental browser standard. It lets a website list named “tools” that an AI agent can call directly, such as
search_productsoradd_to_cart. - Commerce.com enabled it on almost 100,000 domains through Cloudflare’s edge, with no code changes for merchants.
- The agent works inside the shopper’s own browser session. A human still clicks the final checkout button.
- Each merchant can switch it off from the Commerce.com dashboard. Stores that opt out get no injected script and no extra latency.
- Browser support is still limited to Chromium-based previews and origin trials.
What is WebMCP, in plain words?
MCP, short for Model Context Protocol, is a common way for AI models to call outside tools. WebMCP brings the same idea into the browser. A web page registers a short menu of actions, and an agent visiting the page can read that menu and call the actions directly.
Without it, an agent has to scrape HTML, guess which button means “add to bag” and hope the layout doesn’t change. With it, the store just says “here is how you search, and here is how you add to cart.” It’s the difference between handing a delivery driver a map and making them read every street sign.
The spec is being incubated in the W3C Web Machine Learning Community Group. That makes it a draft, not a finished W3C standard. According to Search Engine Journal, Chrome announced an early preview on 10 February 2026 and opened a Chrome 149 origin trial on 9 June 2026. Edge has an origin trial too. Mozilla is neutral on the proposal and WebKit, Safari’s engine, opposes it.
How Commerce.com turned WebMCP on for every store at once
Cloudflare put its edge version of WebMCP into a developer preview in August 2026. When a site owner enables it, Cloudflare adds a small script to each HTML page as the page passes through its network. The script checks whether the browser supports WebMCP and, if it does, registers the site’s tools. Older browsers simply skip it.
Cloudflare’s write-up says the original design had one problem. WebMCP was a single on/off switch per Cloudflare zone, but Commerce.com runs thousands of merchant domains on shared zones through Cloudflare for SaaS. A single switch would have forced every store in or out together.
So the two companies made it per-merchant. Each store’s settings carry an opt-out flag. An edge rule reads that flag and turns WebMCP off for that store only. They also added a setting for a custom MCP address, because Commerce.com’s backend MCP server sits at /api/mcp rather than the default /mcp.
What can an AI agent actually do on these stores?
Picture a shopper asking their browser agent for trail running shoes under $140. Cloudflare’s example shows the agent calling search_products with a query, a maximum price and a size, then add_to_cart with a product ID. Kristina Pototska, Product Management Director at Commerce.com, also lists checking product details and fetching a checkout link.
The agent stops there. The shopper clicks checkout and pays. The tools also run in the shopper’s open tab on the store’s own domain, so the agent sees the same prices and cart, and no login details go to a third party.
“The human shopper stays on the merchant’s site, and the merchant keeps the relationship.”
Kristina Pototska, Commerce.com, via the Cloudflare blog
Commerce.com uses the same tools in its server-side MCP setup, so merchants have one set of tools to look after, not two.
How does this compare with Shopify’s WebMCP rollout?
Commerce.com isn’t first. On 5 August 2026, Shopify switched on WebMCP tools for every Liquid storefront. The two approaches differ in useful ways.
| Commerce.com + Cloudflare | Shopify | |
|---|---|---|
| Went live | Announced 21 October 2026 | 5 August 2026 |
| Scale | Almost 100,000 domains | Every Liquid storefront, plus the Hydrogen preview |
| Delivery | Script injected at Cloudflare’s edge | Built into the Shopify platform |
| Example tools | search_products, add_to_cart, product details, checkout link | 10 tools, including search_catalog, update_cart, proceed_to_checkout |
| Final purchase | Shopper clicks checkout | Agent moves shopper to checkout, doesn’t complete it |
| Merchant control | Per-store opt-out in dashboard | On by default, nothing to configure |
My take: the edge approach is the more interesting part. If Cloudflare can add agent tools to a store without touching its code, any site behind Cloudflare could follow, not just shops on big platforms.
Why merchants and shoppers should care
Commerce.com rebranded from BigCommerce in mid-2025 and moved to the Nasdaq ticker CMRC, betting its future on AI-driven buying, as Digital Commerce 360 reported. Pototska put the pressure plainly: “Merchants keep asking us how they can keep up with agentic shopping.”
For shoppers, structured tools should mean fewer agent mistakes, such as the wrong size or a stale price. For merchants, the risk is losing the customer to an AI middleman. WebMCP’s in-tab design keeps the sale and the relationship on the store’s own site. That matters heading into peak season, when price-hunting behaviour gets intense.
What happens next
Cloudflare says it will keep working on WebMCP as the standard changes, starting with making a site’s tools easier for agents to discover. Browser support is the real bottleneck. Until WebMCP leaves origin trials and Safari and Firefox take a position, most shoppers won’t see it work.
If you build agents, now is a good time to test them against real storefront tools. Our 7-point AI agent evaluation checklist is a solid place to start.
FAQ
Can an AI agent buy something on a Commerce.com store without me?
No. Agents can search, view products, add to cart and get a checkout link, but the shopper completes the purchase.
Which browsers support WebMCP?
Only Chromium-based browsers for now, through Chrome and Edge origin trials, experimental flags and some agentic browsers. Firefox and Safari have no support.
Can a Commerce.com merchant turn WebMCP off?
Yes. A switch in the Commerce.com dashboard disables it for that storefront. No script is injected and no extra latency is added.
Run a store? Open a supported Chromium preview, point an agent at your own storefront and see which tools it finds before your shoppers do.
2 comments