MCP Browser Debugger
Related Servers
Alternatives to MCP Browser Debugger
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive Chrome browser debugging capabilities including DOM inspection, network monitoring, console logs, JavaScript execution, breakpoint debugging, and screenshot capture for AI-assisted frontend development.5MIT
- AlicenseAqualityDmaintenanceEnables reverse engineering of web applications and chat interfaces through browser automation, network traffic capture, and streaming API discovery. Provides comprehensive tools for analyzing network patterns, capturing streaming responses, and automating complex web interactions.148 npm1ISC
- AlicenseAqualityAmaintenanceEnables AI coding assistants to debug and analyze JavaScript code in web pages through breakpoint debugging, function hooking, network analysis, and runtime inspection of scripts including minified code.24722 npm2,825Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.198 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides AI assistants with advanced frontend debugging capabilities through 36 specialized tools for inspecting React/Vue/Angular/Svelte applications. Uses Playwright browser automation and source map intelligence to analyze components, network requests, bundle optimization, and resolve production errors.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.MIT
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, click_element is for clicking, evaluate_xpath for XPath evaluation, get_dom for DOM extraction, and navigate for page navigation—each targets a specific browser debugging action without overlap.
All tool names follow a consistent verb_noun pattern in snake_case, such as click_element, get_cookies, and navigate. This predictability makes it easy for agents to understand and select the right tool based on its naming convention.
With 15 tools, the server is well-scoped for browser debugging, covering essential actions like navigation, DOM inspection, JavaScript execution, and data retrieval. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides complete coverage for browser debugging, including navigation, element interaction, data extraction, and monitoring. There are no obvious gaps; agents can handle full debugging workflows from page loading to inspection and interaction.