A new JavaScript interface that allows web developers to expose their web application functionality as "tools", i.e. JavaScript functions with natural language descriptions and structured schemas that can be invoked by AI agents, browser assistants, and assistive technologies. WebMCP enables collaborative workflows where users and agents work together within the same web interface, leveraging existing application logic while maintaining shared context and user control.

It might be hard to read the tea leaves on this one (so goes developer-focused launches), but the fact that WebMCP is being advanced by both Google and Microsoft is a big deal, and even moreso now that Google is shipping it in Chrome in early preview:

Developers can test WebMCP by enabling the “WebMCP for testing” flag in Chrome 146 Canary at chrome://flags. Google’s Chrome Early Preview Program offers access to documentation, demos, and updates on API changes. With working code already shipping, W3C institutional support, and Microsoft’s co-authorship, WebMCP has cleared the most difficult hurdle any web standard faces: moving from proposal to production software. The foundation is now in place for websites to speak the same structured language that AI agents understand natively.

Expect to see this more widespread by Google I/O in June.

Something I'm wondering is how much better would this WebMCP be than utilizing, for example, Claude codes' ability to do a search? What does this really bring to the table?

WebMCP gave us a much more elegant approach to supporting client-side tool calling in the browser, drastically improving our web app integration story on top of an open standard.

Developers can test WebMCP by enabling the “WebMCP for testing” flag in Chrome 146 Canary at chrome://flags. Google’s Chrome Early Preview Program offers access to documentation, demos, and updates on API changes. With working code already shipping, W3C institutional support, and Microsoft’s co-authorship, WebMCP has cleared the most difficult hurdle any web standard faces: moving from proposal to production software. The foundation is now in place for websites to speak the same structured language that AI agents understand natively.

Expect to see this more widespread by Google I/O in June.

Something I'm wondering is how much better would this WebMCP be than utilizing, for example, Claude codes' ability to do a search? What does this really bring to the table?

WebMCP gave us a much more elegant approach to supporting client-side tool calling in the browser, drastically improving our web app integration story on top of an open standard.

WebMCP

Give AI agents access to web apps via JavaScript

Give AI agents access to web apps via JavaScript

Alternatives Considered

Alternatives Considered