Public Browser
Related Servers
Alternatives to Public Browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.468 npmMIT
- AlicenseBqualityBmaintenanceA browser automation MCP server that enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or vision models.245,425,474 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA token-optimized MCP server that groups Chrome Devtools tools into 8 semantic operations, reducing context window tokens by 69.5% while preserving full functionality.2 npm1MIT
- FlicenseBqualityBmaintenanceUltra-fast browser automation server over Chrome DevTools Protocol (CDP), exposed as MCP, enabling AI agents to control a real Chrome browser with low latency and minimal token usage.212-
- AlicenseNot gradedqualityCmaintenanceThe Zero-Setup Local Browser MCP. Enables AI agents to control web browsers via CDP with zero vision tokens and high-speed DOM mapping.17 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.-
TDQS
Scored across 25 tools
Most tools map cleanly to distinct browser capabilities such as viewing, clicking, typing, scrolling, downloading, and evaluating JS. A few pairs like observe vs wait_for and view_page vs dom_snapshot have some conceptual overlap, but the descriptions do a good job of drawing boundaries.
Names are consistently lowercase and snake_case, but the pattern is mixed: single verbs like click, type, and scroll sit alongside verb_noun names like view_page and fill_form, and noun-style names like virtual_desk, tab_status, and network_monitor. The set is readable but not stylistically uniform.
25 tools is right at the heavy end of a reasonable browser-automation surface. Each tool addresses a legitimate need, but the count feels large, especially with separate tools for screenshots, DOM snapshots, console logs, network monitoring, and evaluate-style operations.
The toolset covers the full browser workflow: tab and navigation management, DOM reading, interaction, forms, waits, dialogs, uploads, downloads, network/console diagnostics, and JavaScript execution. Minor gaps like cookie/localStorage management, explicit frame switching, and hover could cause workarounds but do not block realistic tasks.