Cloudflare gives any site a WebMCP interface with one dashboard toggle — no origin code changes
Cloudflare launched a developer preview of WebMCP on August 6, 2026, using HTMLRewriter at the edge to inject a single bridge script tag into every HTML response, which then registers MCP tools on document.modelContext — the browser surface shipping experimentally in Chrome 146. Tools arrive as opt-in packs (Content Credentials and Site MCP Server ship on by default) declared via a data-packs attribute, and every tool in the preview executes entirely in the visitor's browser with no round trip to Cloudflare, with the Site MCP Server pack calling the origin's own MCP endpoint using the visitor's existing session. Because the bridge emits standard MCP Tool and CallToolResult types, any agent that already speaks MCP can drive the page unmodified; setup lives under Agent Readiness > Labs in the dashboard.
↳ Follow the thread