No user-submitted related servers found.
Scored across 28 tools
Each tool targets a different browser capability, and pairs like browser_network_requests/browser_network_request or browser_snapshot/browser_find are clearly complementary. The only mild ambiguities are browser_type vs browser_fill_form and browser_drag vs browser_drop, but the descriptions are enough to disambiguate them.
Names consistently start with browser_ and are lowercase snake_case, and most follow a verb-first pattern like navigate, click, take_screenshot, and select_option. A handful of resource-style names such as tabs, network_requests, console_messages, snapshot, and jev_status break the verb_noun pattern, but the shared prefix keeps the set predictable.
28 tools exceeds the 25-tool threshold and feels heavy, especially with granular near-duplicate primitives such as drag/drop, type/fill_form, and snapshot/find plus JEV/WebMCP-specific tools. Some tools earn their place, but the surface could be consolidated without much loss.
The surface covers the core browser automation lifecycle: navigation, interaction, forms, uploads, waits, snapshots, console/network inspection, and tab/page management. Minor gaps like reload/forward, cookie/localStorage management, and download handling can be worked around via browser_evaluate or browser_run_code_unsafe.
