browser-control
Related Servers
Alternatives to browser-control
- AlicenseNot gradedqualityDmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.316MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.83MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables AI assistants to control Chrome DevTools via CDP for debugging tasks like navigation, screenshots, and JavaScript execution.MIT
- AlicenseNot gradedqualityDmaintenanceA Chrome DevTools Protocol-based MCP server that enables AI coding assistants to control browsers for JavaScript debugging, reverse engineering, web scraping, and API debugging.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that lets coding agents control and inspect live Chrome browsers, providing full Chrome DevTools capabilities for automation, debugging, and performance analysis.2,158,323 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server for debugging Electron apps: discover, launch, and control apps via Chrome DevTools Protocol and Node inspector, enabling JavaScript evaluation, network/console monitoring, screenshots, profiling, and breakpoints.441MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.2-
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.69 npm52MIT
TDQS
Scored across 31 tools
Most tools have clearly distinct purposes (click vs fill vs press_key vs hover vs drag; snapshot vs inspect_dom; console vs issues vs network logs). The main blur is among lifecycle tools: stop_browser, restart_browser, and close_instance overlap in meaning, and fill_input vs fill_form require reading descriptions to separate. These are minor compared with the strongly partitioned rest of the surface.
Dominant snake_case verb_noun pattern (capture_screenshot, open_tab, get_network_logs, list_downloads) with predictable prefixes for read/list/create lifecycle. Deviations exist: bare verbs (hover, drag, scroll, reload, resume, navigate) and a lone noun (snapshot), but the grouping remains readable and predictable.
31 tools is heavy for a browser server, though the breadth (interaction, DOM, network, console, CSS, tabs, instances, downloads, debugging) justifies much of it. Some consolidation is possible - stop_browser/restart_browser vs close_instance, and find_in_snapshot as a helper to snapshot - so the count is borderline rather than well-scoped.
Coverage is unusually thorough: navigation, snapshot/DOM inspection, full input simulation, network and console logs, browser-diagnosed issues, CSS inspection, dialogs, debugger pauses, and instance/tab/download management. Gaps remain around file uploads, cookie/storage/state management, and network interception or viewport/device emulation, which agents will occasionally need.