$ loading_
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "MCP Chrome Debugger Protocol" yet — see the docs or source repo.
Connect to the running Node.js process, inspect the current call stack, breakpoint hits, and exception details, then identify the root cause of this runtime error and suggest a fix.
A diagnosis with stack analysis, likely code locations, and recommended fixes.
Connect to this Node.js service, trace an asynchronous request from entry point to database call, observe key variable changes, and summarize where state becomes inconsistent or the logic breaks.
A mapped async call flow, key state changes, and analysis of where the issue occurs.
Use the debugging protocol to connect to a Node.js process in staging, inspect thread and breakpoint information, and check whether a slow API response is caused by blocking, infinite loops, or resource waits.
An initial diagnosis of the performance bottleneck, clues about blocking locations, and next debugging steps.
Automate Chromium for web actions, debugging, and browser testing tasks.
Connect Chrome DevTools so AI can debug pages and inspect performance.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.
Control Chrome for debugging, automation, and performance analysis via DevTools.
Control a real Chrome browser for browsing, interaction, and page reading.
Control and inspect live Chrome for automation, debugging, and performance analysis.