No user-submitted related servers found.
Scored across 35 tools
The core interaction tools (click, type, press, scroll, drag, select, upload) are cleanly separated, but the perception layer has four overlapping channels: browser_snapshot, browser_read, browser_extract and browser_screenshot all return page content, and browser_find vs browser_element_at vs browser_cursor all locate elements by different means. browser_wait and browser_watch both wait for page changes, and browser_cursor vs browser_cursor_style differ only subtly in name while doing unrelated things.
Every tool carries the same browser_ prefix and uses snake_case throughout, which makes the set highly predictable. The only inconsistency is grammatical: many names are verbs (navigate, click, extract, replay) while others are nouns (snapshot, tabs, events, history, stats, recipes, cursor), though each remains readable and guessable.
35 tools is well past the comfortable range for a single server and the surface sprawls into four sub-domains: core automation, perception, diagnostics (trace, stats, console, events), and a teaching/recording subsystem (teach_start, teach_stop, recipes, replay, record_start, record_stop). Several of these are convenience wrappers or observability extras that could be collapsed (batch, cursor_style, stats, trace) rather than separate tools.
The surface is unusually thorough: navigation, tabs, full input primitives, human handoff, downloads/dialogs, structured extraction, batch execution and a recipe-recording lifecycle are all covered with no obvious dead ends. Remaining gaps are real but niche for the domain: no iframe/frame targeting, no cookie or localStorage management, no viewport/device emulation, and no clipboard read beyond keyboard shortcuts.