The current spec is geared toward Human-in-the-Loop which is unofficially interpreted as "the agent lives in the context of the browser" (browser's agent, extension agent, Iframe agent etc). We initially elected that external agent browser automation cases be out of scope (see #21 and the 2025-09-18 resolution) and that WebMCP focuses on human-in-the-loop use cases initially. However, from what I've seen, a large part of the excitement around this API is geared toward remote browser automation over things like WebDriver BiDi / CDP.
Source: Cloudflare supports WebMCP-enabled browsers on their Browser Run platform
They also released an interesting Human-in-the-Loop feature that got me thinking about what a first-party integration between WebMCP and a non-browser-native client might look like. The user might be present but driving from outside the browser, so does this fall into our Human-in-the-Loop domain?
It might look something like this:
The current spec is geared toward Human-in-the-Loop which is unofficially interpreted as "the agent lives in the context of the browser" (browser's agent, extension agent, Iframe agent etc). We initially elected that external agent browser automation cases be out of scope (see #21 and the 2025-09-18 resolution) and that WebMCP focuses on human-in-the-loop use cases initially. However, from what I've seen, a large part of the excitement around this API is geared toward remote browser automation over things like WebDriver BiDi / CDP.
Source: Cloudflare supports WebMCP-enabled browsers on their Browser Run platform
They also released an interesting Human-in-the-Loop feature that got me thinking about what a first-party integration between WebMCP and a non-browser-native client might look like. The user might be present but driving from outside the browser, so does this fall into our Human-in-the-Loop domain?
It might look something like this: