ML.
/

Browser-automation

WebMCP Explained: What Changes in Browser Automation When a Web Page Hands Tools Directly to an AI Agent?

WebMCP is a W3C Community Group proposal in which a web page registers JavaScript functions and HTML forms as "tools" on document.modelContext, and the browser mediates those tools to the user's agent. This article lays out the imperative and declarative APIs and the boundaries the browser guarantees, straight from the spec, then calls real tools with Chrome 152 and agent-browser 0.36 to see how it differs from accessibility-tree automation.

webmcpbrowser-automationai-agentchromeweb-standardsagent-browsermcpe2e

Analyzing Browser Use: How Do You Show a Web Page to an LLM So It Can Drive a Browser?

Browser Use is a Python agent in which an LLM drives a real browser. It pre-chews the page into an indexed list of interactive elements for the LLM, drives the browser via CDP instead of Playwright, and runs the session with an event bus and watchdogs. We look at why this fits LLMs better, picking up from the earlier Playwright analysis.

browser-usebrowser-automationai-agentcdpplaywrightllme2earchitecture