Overview
- Cloudflare said it injected a small WebMCP script at the edge so Commerce.com can expose structured shopping tools across almost 100,000 storefront domains without merchants editing their sites.
- WebMCP gives agents discoverable functions such as search_products and add_to_cart so agents can call site tools directly instead of simulating clicks on page HTML.
- Commerce.com and Cloudflare built per-merchant opt-outs using hostname metadata and Configuration Rules so individual stores can disable WebMCP with no added latency or injected script.
- The injected bridge proxies Commerce.com’s backend MCP tool definitions unchanged and runs inside the shopper’s browser session so agents see the same cart and prices and no customer credentials go to third parties.
- WebMCP remains an experimental preview with limited browser support behind Chrome flags and origin trials, with safe fallbacks when a store’s MCP server is offline and no public usage figures yet; the rollout signals a broader move toward agent-native shopping that could change how merchants manage checkout, privacy, and liability.