Yeah, this seems like a weird niche where an agent has to interact with an existing browser session.

That, or they expect that MCP clients should also be running a headless Chrome to detect JS-only MCP endpoints.