BrowserAgentofficial
A
licenseB
qualityA
maintenanceMCP server for Puppeteer-based browser automation with a unified observe (a11y snapshot + pixel overlay), diff engine, event layer, and action primitives.
26
46 npm
Apache 2.0
No user-submitted related servers found.
Scored across 3 tools
Each tool has a distinct action: open, run, close. No overlap; an agent can easily select the correct tool for each step of the browser lifecycle.
All names follow the exact pattern `browser_tab_<verb>`, with verbs being clear actions. Perfectly consistent.
Three tools cover the essential browser tab lifecycle: open, execute code, close. This is a well-scoped set for the server's purpose.
The tools cover the primary workflow (open, run, close). While additional tools for specialized actions (e.g., tab navigation) could be added, the API methods described in the critical rules provide sufficient interactivity, so no dead ends.