WebMCP just shipped in Chrome 146. Here's what it means for screenshot APIs.

WebMCP just shipped in Chrome 146. Here's what it means for screenshot APIs. Google shipped WebMCP in Chrome 146 Canary last week. It is a real thing, the coverage is accurate, and if you build anything that touches browser automation or AI agents, you should understand what it does. Here is the short version: WebMCP is a proposed W3C standard, built jointly by Google and Microsoft, that lets websites expose structured callable tools directly to AI agents through a new browser API ( navigator.modelContext ). Instead of an agent scraping the DOM or simulating clicks, the website declares what it can do and the agent calls it directly. Think of it as MCP, but running inside the browser tab rather than on a separate server. The early preview is Chrome 146 Canary only, behind a flag. Stable Chrome is months away. Meaningful site adoption is further out than that. What WebMCP actually covers The canonical example from the spec: a travel site exposes a searchFlights() tool. An AI agent calls