What it does
browserdebug provides Chrome DevTools-style debugging in one binary, usable either as a CLI or as a stdio MCP server. It can record performance traces and read their insights, list and inspect network requests, read console messages, take text snapshots and screenshots, emulate network, CPU and device conditions, and drive page input by element uid. The MCP server exposes 26 tools, including click, fill, navigate_page, evaluate_script and take_screenshot.
It suits developers who want to inspect and debug web pages running in Chrome, from a terminal or from an MCP-capable AI client. Its performance-trace workflow requires a trace to be started before it can be stopped and prevents it from being started twice. CLI exit codes are 0 for success, 1 for browser errors and 2 for usage errors.
The package bundles no browser and downloads none. A deployment must inject a DevTools-protocol-compatible executor, defined by the DebugBrowser interface in src/types.ts, to drive a real Chrome. Without one, browser commands fail with a "Browser unavailable" error.
Limitations and requirements
Browser commands need a DevTools-protocol-compatible executor injected by the deployment to drive a real Chrome. The package does not include or download a browser, and without an executor, browser commands fail with a "Browser unavailable" error.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/browserdebug
Debug web pages in Chrome: performance traces, network, console, snapshots, screenshots.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it