Chrome MCP
Related Servers
Alternatives to Chrome MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.737 PyPIGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.497 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables driving a real Chrome instance remotely through MCP, including per-tab control, JavaScript evaluation, screenshots, cookie and network capture, and CDP fallback with token-based authentication.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceExposes browser tabs to any MCP client through a local broker, letting agents discover pages, take text snapshots with numbered elements, and drive them via click, type, navigate, eval, network/log inspection, and screenshots. Supports stdio, Streamable HTTP, and SSE transports so IDE and CLI agents can orchestrate browser automation.MIT
- AlicenseNot gradedqualityBmaintenanceLets coding agents control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis. Provides access to Chrome DevTools capabilities such as tracing, network inspection, screenshots, and console messages through MCP clients.1,924,448 npmApache 2.0
TDQS
Scored across 28 tools
Most tools target clearly distinct actions (navigate, click, fill, scroll, screenshot, network, console). A few pairs are close—wb_fill vs wb_type (replace vs insert) and wb_snapshot vs wb_get_text vs wb_find—but descriptions explicitly disambiguate them, and wb_close_tab vs wb_close_session differ in scope.
Uniform wb_ prefix and predominantly verb_noun patterns (wb_navigate, wb_click, wb_find_tab, wb_close_session). Minor deviations: wb_status, wb_snapshot, and wb_screenshot are noun-style rather than verb-first, but the convention remains predictable overall.
28 tools is on the heavy side of the rubric, though browser automation is a genuinely broad domain. Most tools earn their place (navigation, tabs, read, interact, observe), but lower-frequency ones like wb_dblclick, wb_hover, and wb_drag push the surface toward bloat.
Strong coverage of the browser lifecycle: navigate/history/reload, tab and session management, reading (snapshot/text/find), full interaction set, plus network, console, screenshot, and upload. Gaps remain for cookies/storage, download handling, JS dialog/alert handling, and iframe targeting, which agents may hit in real workflows.