F
licenseNot graded
qualityD
maintenanceMCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.
-
chrome-dev-mcp
by congzhou09
Related Servers
Alternatives to chrome-dev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI coding agents control and inspect a live Chrome browser, providing reliable automation, debugging, and performance analysis through Chrome DevTools.44 npmApache 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,457,419 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceA local MCP server that connects to a Chrome extension to enable AI agents to control browser tabs, execute automation, and interact with web pages via tools.-
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables AI assistants to control Chrome DevTools via CDP for debugging tasks like navigation, screenshots, and JavaScript execution.-
- -licenseNot gradedqualityNot gradedmaintenanceMCP server that connects AI agents to a real Chrome browser via a WebSocket extension bridge, enabling over 40 browser control tools without debug mode or profile isolation.-
TDQS
A4.2/5.0
Scored across 24 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: page inspection, execution evaluation, debugging control, breakpoint management, tab switching, console/network capture. Even the closest pair (get_scope_variables vs evaluate_at_frame) is well separated by description: one lists variables in scope, the other evaluates arbitrary expressions in that scope.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern: get_*, list_*, set_*, remove_*, pause_*, resume_*, step_*, evaluate_*, screenshot, clear_*. The verbs are specific and predictable, making the set easy to navigate.
Tool Count4/5
At 24 tools, the server is on the heavier side, but the breadth is justified by the Chrome DevTools domain: debugging, DOM access, console, network, and tab management. Each tool addresses a distinct need, so the count feels slightly over a typical 3–15 scope but reasonable for a full-featured DevTools integration.
Completeness4/5
The surface covers the core workflows: page inspection, script evaluation, breakpoint debugging, stepping, console and network capture. Minor gaps exist—no conditional breakpoints, no full-page screenshots, no network interception—but these are workarounded via evaluate_js or are explicitly documented limitations.
Maintenance
ActivityActive
ResponsivenessResponsive