WebMCP goes live on almost 100,000 commerce storefronts
Cloudflare and Commerce.com switched on an experimental agent-shopping standard at the edge, with no code changes required from most merchants.
Cloudflare said on 21 October that WebMCP, an experimental browser standard for giving AI agents structured tools on a page instead of making them guess at buttons and HTML, is now live on almost 100,000 Commerce.com storefronts. Instead of an agent clicking blindly through a checkout flow, it calls a defined tool such as search_products directly.
Cloudflare injects the bridge script at the edge, so most merchants need to change nothing. A data-mcp-url attribute lets a store point the bridge at a custom backend path, Commerce.com uses /api/mcp rather than the default /mcp, and merchants can opt out entirely through Configuration Rules. If the MCP server is offline or the shopper’s browser doesn’t support WebMCP, the storefront just loads as normal.
<script type="module"
src="/.webmcp/bridge.js"
data-packs="c2pa,mcp-server-client"
data-mcp-url="/api/mcp"></script>
Why it matters: this is the largest live deployment of WebMCP so far, and it shows the pattern for adding it to a site without a rewrite: an injected script plus a path to your own MCP endpoint. Anyone building a storefront, or an agent meant to shop on one, now has a working reference rather than a spec to guess from.
The caveat: WebMCP is still an experimental proposed standard, reachable today only through Chrome flags, Origin Trials or select agentic browsers, not something a typical visitor’s browser supports yet.