Commerce.com just flipped the switch on nearly 100,000 WebMCP endpoints simultaneously. Each storefront now exposes a uniform agent interface for browsing, cart management, and checkout, while preserving per-merchant authorization boundaries and existing payment flows. This is the largest known deployment of Model Context Protocol servers in a transactional, multi-tenant environment.

The deployment runs entirely on Cloudflare Workers, which means MCP servers execute at the edge with no central bottleneck. The architecture solves three hard problems: routing agent requests to the correct merchant backend, enforcing isolation between storefronts, and delegating payment orchestration back to each merchant's existing checkout flow instead of centralizing it.

Why WebMCP Instead of REST APIs

Commerce.com could have exposed traditional REST endpoints for each store. WebMCP gives them something different: a standardized tool discovery protocol that AI agents already understand.…