TLDR;
Cloudflare and Commerce.com have enabled WebMCP across almost 100,000 storefront domains, with eligible BigCommerce stores switched on by default and able to opt out. Compatible browser agents can call structured product and cart tools instead of guessing at buttons, while the shopper completes checkout on the merchant site. The reach is meaningful, but WebMCP still depends on preview-stage browser support and each store's enabled tools.
What happened
Cloudflare says the WebMCP deployment now reaches almost 100,000 Commerce.com storefront domains. The edge layer injects a bridge script that exposes the store's existing server-side MCP tools through the shopper's browser session. Commerce.com's announcement says eligible BigCommerce merchants receive it by default, with a control-panel setting to turn it off.
BigCommerce explains how browser agents can search products, manage a cart and return a checkout link. The agent works against the same storefront domain and session the shopper is using, so the merchant retains its checkout, customer relationship and commerce rules. Signed-in B2B buyers can also receive tools tied to their account permissions, such as shopping lists and quotes, when the relevant server-side MCP is enabled.
The limitations are material. The developer documentation states WebMCP remains dependent on preview browser support, with Chrome and Edge listed as preview environments. Stores without server-side Storefront MCP expose only a smaller default tool set. If an MCP service is unavailable or the browser does not support WebMCP, the bridge exits and the ordinary human storefront continues to load.
Why it matters
This is a practical move from agentic commerce demonstrations toward platform-scale deployment. BigCommerce merchants do not have to rewrite themes or install a new storefront application merely to make structured actions discoverable. Cloudflare can add the bridge at the edge across shared infrastructure while Commerce.com keeps the business logic in its own MCP servers.
That architecture also draws a useful boundary. The browser agent can help with discovery and cart building, but it does not receive raw payment credentials or bypass the merchant checkout. Brands keep control of price, inventory, eligibility, promotions and final order validation. For regulated or complex retailers, that is a safer starting point than allowing an external agent to transact through a separate marketplace.
Default enablement still creates operational responsibility. An inaccurate catalogue, stale stock, incorrect B2B entitlement or unsafe tool description becomes machine-readable at scale. The agent may call exactly what the store exposes, so teams must treat tool contracts as a customer-facing interface. Security, product, legal and commerce owners need a shared approval process rather than assuming the feature is only a frontend enhancement.
How your brand can benefit / be affected
First, confirm whether your storefront is eligible and whether WebMCP is enabled. Inventory the tools exposed to guests, signed-in consumers and B2B buyers. Test product search, variant selection, cart updates, personalized prices and checkout handoff using non-production orders. Check that failures fall back cleanly to the standard site.
Second, review the data and permissions behind each tool. Product identifiers, availability, currency, customer groups, tax context and promotion rules should match what a human sees. Avoid exposing internal fields simply because they are convenient for a backend service. Log tool calls separately from ordinary page events so you can distinguish agent-assisted journeys from human browsing without overstating attribution.
Finally, make the opt-out decision deliberately. Brands with accurate catalogues and well-governed storefront MCPs may gain an early discovery advantage from compatible agents. Brands with complex contractual pricing, fragile integrations or unresolved consent questions may need a narrower tool set or temporary opt-out. The right test is whether an agent can complete a useful shopping task with the same controls and commercial truth as the storefront, not whether a WebMCP flag is technically on.
News date: 21 October 2026. Editorial review: 30 October 2026.