No user-submitted related servers found.
Scored across 25 tools
Each tool maps to a distinct browser primitive (snapshot vs screenshot, click vs type vs hover vs drag, console vs network), and the descriptions explicitly state when to prefer one over another. The only soft overlaps are browser_open / browser_navigate / browser_tab_new (all take a URL) and browser_show vs browser_scroll-into-view, but the descriptions clarify the distinction well enough.
All tools share a consistent browser_ prefix with snake_case, and most follow verb_noun (browser_click, browser_type, browser_navigate, browser_get_selection). The tab family deviates to noun_verb (browser_tab_new, browser_tab_select, browser_tab_close) and browser_status / browser_console are bare nouns, but the grouping is still readable and predictable.
25 tools is at the upper edge, but for full in-browser automation each primitive (click, hover, drag, type, key press, select, upload, dialog, scroll) genuinely earns its place rather than being redundant. A few could arguably be folded together (tab_open into open, status into tabs), but the surface is not padded.
The lifecycle is well covered: open/share/navigate tabs, read the page, interact, wait, inspect console/network, evaluate JS, and pick elements. Gaps are minor but real — no cookie/localStorage access, no download handling, no viewport resize, and no explicit iframe entry beyond inline refs.