Commerce.com turns on WebMCP for nearly 100,000 storefronts

Description and use

Commerce.com enabled WebMCP for nearly 100,000 storefronts, letting agents use structured tools instead of parsing HTML.

Problem

Shopping agents rely on fragile HTML parsing, leading to slow, token‑hungry, and theme‑breakable interactions.

Outcome

WebMCP enables efficient, reliable agent interactions across ~100,000 Commerce.com storefronts without requiring site‑owner code changes.

Workflow

• Enable WebMCP edge script via Cloudflare
• Configure per‑merchant opt‑out rule in Commerce.com dashboard
• Set custom MCP path (/api/mcp) in Cloudflare zone settings
• Agents discover and invoke WebMCP tools on storefronts
• Shopper completes checkout manually

Evidence

Most shopping agents today work from a site's HTML. They look at the page, guess what each control does, click, and retry on failure.

Source

WebMCP is a Google-backed browser standard that gives a page structured tools, such as search_products.

Source

Two changes were needed for a platform of this size: Per‑merchant opt‑out and Custom MCP path.

Source