JA EN
shiichan

Nearly 100,000 Stores Go Agent-Ready: Commerce.com and Cloudflare Roll Out WebMCP

Cloudflare Blog ★★★ View Markdown
#cloudflare#ai#web

Hi everyone, Shii-chan here! Stores are getting ready for AI agents that shop, and there's a big step forward to share.

Cloudflare Blog blog.cloudflare.com

What was announced?

The Cloudflare Blog describes how almost 100,000 Commerce.com storefront domains now give AI agents real shopping tools through WebMCP on Cloudflare. Commerce.com is a commerce platform that already runs its almost 100,000 domains on Cloudflare. The post explains how they turned it on across every store at once while keeping each merchant in control.

The story so far

Shopping agents today usually work from a site's HTML. They guess which buttons to click and retry on errors, which is slow, token-heavy, and fragile. A theme change can break it.

WebMCP is an experimental browser standard from Google that exposes tools such as search_products directly to the agent. It's in early preview, available behind a Chrome flag (chrome://flags/#enable-webmcp-testing), in Chrome Origin Trials, in some agentic browsers, and in developer environments such as Cloudflare Kitesurf.

What changes

  • Agents call a store's tools directly instead of guessing at buttons
  • Merchants can show up in agent-driven answers without rebuilding their sites
  • Merchants keep the customer and checkout control

Kristina Pototska, Product Management Director at Commerce.com, said merchants want to appear in agent-driven answers while keeping the customer, keeping checkout control, and avoiding a site rebuild.

Dive Deep

Architecture

  • WebMCP tools run inside the shopper's active browser session on the storefront's domain. The agent sees the same prices and cart, no credentials go to a third party, and the visit stays on the merchant's site
  • Cloudflare acts as the edge delivery layer for Commerce.com's backend MCP server, proxying tool definitions and actions unchanged, so merchants keep control of tool logic
  • Commerce.com's server-side MCP serves agents that connect to a store directly, while WebMCP serves agents running in the shopper's browser. Both expose the same shopping tools, so merchants don't manage two sets
  • In August, Cloudflare launched an edge implementation of WebMCP in beta. When enabled, Cloudflare injects a small script at the edge, so site owners write no code

Example flow

For a request like finding a waterproof trail running shoe under $140 in size 10 and adding it to the cart, the agent:

  • Detects the store's tools on document.modelContext
  • Calls search_products({ query: "trail running shoe", max_price: 140, size: 10 })
  • Calls add_to_cart({ product_id: "shoe_123" })

The cart updates in the live session, and the shopper completes payment by clicking checkout themselves.

Rollout challenges and solutions

WebMCP was designed as a single on/off switch for an entire zone. But Commerce.com hosts thousands of merchant vanity domains on shared zones through Cloudflare for SaaS.

  • Platform-wide enablement with per-merchant opt-out: WebMCP is enabled on the main zone, and Configuration Rules plus custom hostname metadata do the rest. When webmcp_opt_out equals "true", a rule sets webmcp_enabled to false for that storefront. Merchants flip the switch in the Commerce.com dashboard. Rules run at the edge before the page is served, so opted-out stores see no added latency, no remote lookups, and no injected scripts
  • Custom MCP endpoint paths: the bridge initially expected each site's MCP server at /mcp, but Commerce.com's is at /api/mcp. Cloudflare added a zone-level configurable MCP URL setting, passed to the script as data-mcp-url. The injected script is /.webmcp/bridge.js with data-packs="c2pa,mcp-server-client"
  • Graceful fallback: if a store's MCP server is offline or the browser doesn't support WebMCP, the script exits and the storefront loads normally for human shoppers

Looking ahead, Cloudflare and Commerce.com plan to keep investing as the standard evolves, starting with making it easier for agents to discover a site's tools. A panel titled "Getting your storefront agent ready for peak season" is scheduled for Cloudflare Connect in San Francisco on October 21, 2026.

Wrap-up

  • WebMCP on Cloudflare is now on across almost 100,000 Commerce.com domains
  • Tools run in the shopper's browser session, and the shopper completes checkout
  • Configuration Rules and metadata combine platform-wide enablement with per-store opt-out
  • The MCP endpoint path is configurable, with a safe fallback when unsupported

If you run an online store or build agent-ready websites, this case study is for you!

Related posts