How Commerce.com and Cloudflare are getting storefronts ready for AI agents
- ID
- 37852
- Status
- summarized
- Published
- 21 Oct 2026, 9:00 PM
- Fetched
- 21 Oct 2026, 9:38 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/webmcp-commerce/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.0
- Created
- 21 Oct 2026, 9:41 PM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Cloudflare has a beta edge implementation of WebMCP, Google's experimental browser standard that exposes structured tools like search_products to AI agents instead of forcing them to scrape HTML and guess at buttons. Commerce.com, which runs almost 100,000 domains on Cloudflare, is turning WebMCP on across all its storefronts at once with per-merchant edge opt-outs, so agents can search products, build carts, and get checkout links without merchants editing themes. WebMCP is still behind Chrome flags and Origin Trials and works alongside server-side MCP.
Why it matters
If you run a commerce platform or many storefronts, the concrete pattern here is platform-wide edge injection plus per-merchant opt-outs, not asking every merchant to edit a theme. But because WebMCP is still behind chrome://flags/#enable-webmcp-testing and Origin Trials, prototype the agent-tool contract now rather than treating it as a production requirement.
Discussion angle
When a platform enables agent tools across all stores by default, who should control opt-in, checkout, and the merchant-customer relationship?