No user-submitted related servers found.
Scored across 16 tools
Most tools target clearly distinct purposes: browser lifecycle, element inspection, diagnostics, and action execution. A couple of pairs could be confused—get-context-info vs. get-context-stats and execute-browser-commands vs. browser-evaluate—but the descriptions provide enough separation.
Tool names mostly follow a consistent lowercase hyphenated verb-noun pattern like start-browser, list-browsers, and capture-screenshot. browser-evaluate breaks the pattern by placing the noun first, and how-to-use is a nonstandard meta tool, but overall the convention is predictable.
At 16 tools, the server is slightly above the ideal range but each tool maps to a legitimate browser automation capability. Some could be consolidated, such as the element getter tools or context info/stats, but the count is still reasonable for the scope.
The server covers the main browser automation workflow: lifecycle management, interaction via commands and evaluation, element inspection, screenshots, network monitoring, and console/HMR diagnostics. Minor gaps exist, such as no standalone navigation tool outside execute-browser-commands and no explicit tab or cookie management, but agents can work around these.