WebMCP browser APIs could reduce web scraping needs for AI agents

What WebMCP changes for web automation

Google recently released WebMCP, two new browser APIs that enable websites to register tools that AI agents can call directly. Instead of scraping DOM elements or fighting anti-bot systems, sites can expose their functionality through standardized interfaces.

How it works technically

Sites register tools using navigator.modelContext.registerTool() with a name, description, input schema, and execute function. The source provides this example:

navigator.modelContext.registerTool({
  name: "search_flights",
  description: "Search available flights",
  inputSchema: { /* JSON Schema */ },
  execute: async (input) => {
    return await internalFlightAPI(input);
  }
});

This approach eliminates CSS selector chains, retry logic, headless browser session management, and DOM scraping for any site that implements WebMCP.

Current implementation status

The spec is still in early stages - the W3C draft contains literal "TODO: fill this out" comments in method definitions. It's currently available in Chrome 146 only as an early preview. The author has signed up for the early preview to test how much of their existing scraping code can be replaced.

Practical implications for developers

For developers already building MCP servers, the mental model is identical: tools + schemas + execution. The jump from exposing local resources as MCP tools to websites exposing themselves as MCP tools is small - same architecture, different transport.

Big sites with existing internal APIs (like Booking, Amazon, airlines) are likely to adopt first since they can expose their APIs through WebMCP with minimal changes. Scrapers won't disappear entirely - sites without WebMCP implementation will still require traditional approaches.

The author suggests a tiered approach: agents try WebMCP first, fall back to DOM automation if unavailable, then fall back to raw scraping as last resort - using the best available method per site.