Why it matters
A community speaker presented WebMCP, a proposed web standard in Chrome, as a way to tell AI agents which actions a site offers, such as booking an appointment, so they do not have to scrape the interface. It has declarative tools, annotations on standard HTML forms, and imperative tools defined in JavaScript; at the event it was not supported by all browsers but could be enabled for testing. It plays no documented role in Google Search.
How to meet it
Pilot it on one task flow: annotate an existing form for the declarative API or register a JavaScript tool for booking, filtering or adding to cart, through Chrome's origin trial (Chrome 149 and later) or the chrome://flags/#enable-webmcp-testing flag. Keep the normal HTML flow working for users and agents without WebMCP.
How to test it
With the flag enabled, Chrome's tooling lists the site's tools, and the flow still completes without WebMCP.
How Regensbot covers it
Decided automatically once Regensbot renders your pages.
Headless Chromium renders the page on an isolated render service, and the raw and the rendered HTML run through the same parsers.
Sources
Google documents01
Claims in the knowledge base04
- D1-C281ConfirmedLightning session A: Automation and AISaid on stage
- D1-C282ConfirmedLightning session A: Automation and AISaid on stage
- D1-C283ConfirmedLightning session A: Automation and AISaid on stage
- D1-C316SourceLightning session A: Automation and AIGoogle's documentation
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Confirmed
- Google's documentation states the same thing.
- Source
- The claim is the cited document itself.