Repository navigation
Is it compatible with webMCPs? Would agents be able to discover and use webMcps through this too? #2635
Replies: 1 comment
|
Yes, it already supports it (experimental). It was added in 0.36.0, and I checked against 0.43.0 (commit eb19c9a). It's on by default for Chrome that agent-browser launches itself. When a page registers WebMCP tools, normal browser responses announce them (name, short description, origin, frame id), and you fetch the full schema only when you need it: If several frames register the same tool name, pass For agents using it as an MCP server: the tool catalog shows up in ordinary results, but to let the agent actually invoke the tools you have to enable the webmcp tool profile: Limits: attached browsers, remote providers, Lightpanda, Safari/iOS and older Chrome builds may not expose the CDP WebMCP domain, and then you get a |
Uh oh!
There was an error while loading. Please reload this page.
Hi guys!
Is this already compatible with webMcp? Discovery, tool calls and so on?
All reactions