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.246 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.246,524,222 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.14 npm1MIT
- FlicenseBqualityCmaintenanceUltra-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
Each tool has a clear, singular purpose with minimal overlap. view_page and dom_snapshot are distinct (text/refs vs layout/geometry), and capture_image is explicitly limited to pixel-level content. The descriptions reinforce boundaries, so an agent should rarely misselect.
The majority follow a verb_noun pattern (view_page, file_upload, fill_form, switch_tab), but there are single verbs (type, click, scroll, evaluate) and noun-only names (virtual_desk, console_logs). The consistent snake_case and predictable verb-first style keep it readable, though not perfectly uniform.
At 25 tools, this is on the heavy end of the appropriate range. However, each tool addresses a distinct browser automation capability (navigation, interaction, waiting, dialogs, downloads, JS execution, network, etc.), so the count is justified by the breadth of the domain.
The surface is remarkably complete for browser automation: navigation, tab management, clicking, typing, forms, drag-and-drop, scrolling, waiting, dialogs, downloads, screenshots, DOM inspection, JS execution, network monitoring, console logs, file upload, session config, and batch evaluation. No critical gaps are apparent.