Debug Web MCP
Related Servers
Alternatives to Debug Web MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to inspect and drive Electron or Chrome/Chromium apps via the Chrome DevTools Protocol, exposing DOM snapshots, console logs, network requests, and gated interactions like clicking, typing, and navigating.651 npm1MIT
- 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,440,876 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables AI to interact with Chrome DevTools Protocol to inspect and debug live web pages, including DOM, styles, console logs, and network requests.111,440,876 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis.1,440,876 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis via Chrome DevTools.1,440,876 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.1,440,876 npmApache 2.0
TDQS
Scored across 8 tools
Each tool has a distinct purpose, but browser_list_network_requests and browser_get_events both query captured network data, causing minor overlap. Descriptions help clarify that one is network-focused metadata and the other is all event types.
All tools follow a consistent browser_verb_noun pattern using snake_case. Names are predictable and readable throughout.
Eight tools are well-scoped for a browser debugging server, covering session and capture lifecycles without excess. Each tool earns its place.
Session lifecycle (list, open, close) and capture lifecycle (start, stop, query) are fully covered. Missing operations like page evaluation or DOM inspection are minor gaps for a capture-focused debugging tool.