agent-browser-mcp tested by Argusic Runner

What the test found

In a fresh .venv the project installs and builds, its CLI prints help/extension path/hermes config/doctor JSON, its MCP stdio server responds to initialize and tools/list with 19 tools, and against a mock Chrome bridge list_tabs, execute_js, scan_page, page screenshot, and desktop screenshot all returned real results, with the generated PNGs decodable by ffmpeg.

Standard install required a venv (PEP 668) and mcp<2 pin (FastMCP v1 import). Real Chrome/extension path not exercised (no browser binary in container); verification used a schema-correct mock extension. doctor http_port_open is a false negative. pointer_info returns null in this headless container. Repo edits: pyproject.toml mcp<2, tmwebdriver.py is_remote init-order fix.

Argusic installed agent-browser-mcp in 28 minutes and launched it; verification reached Verified with mock services. 3 of 3 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of agent-browser-mcp

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.