What is Chrome Debug Mcp?
Chrome Debug Mcp is an asynchronous Rust-based Model Context Protocol (MCP) server that allows AI agents and large language models to natively control, automate, and debug Chromium-based browsers via the Chrome DevTools Protocol (CDP). Using cdp-lite, it hooks directly into the browser without heavy abstractions, and starting from v0.2.0 can manage the Chrome process lifecycle automatically.
How to use Chrome Debug Mcp?
Install via pre‑compiled binaries from the Releases page, via Cargo (cargo install --git https://github.com/raultov/chrome-debug-mcp), or with a shell script (Unix). Configure any MCP client (Claude Desktop, Gemini CLI, ChatGPT CLI) using a JSON configuration that specifies the executable or Docker command. You can run it natively, in Docker (headless), or in a hybrid mode where the container controls a Chrome instance on the host.
Key features of Chrome Debug Mcp
- Local‑only navigation restriction (
--local) for security
- Send raw CDP commands (
send_cdp_command) as a fallback
- Automatic Chrome instance management (auto‑launch, restart, stop)
- Proxy authentication handling (
enable_proxy_auth)
- User input simulation (click, fill, scroll)
- Network log interception with advanced filtering
- Console log retrieval with level filtering
- Performance metrics and Core Web Vitals profiling
- Live debugging with breakpoints, step‑over, and resume
Use cases of Chrome Debug Mcp
- Debugging web applications from an LLM‑powered editor or chat interface
- Automated browser testing with natural language instructions
- Performance profiling and Core Web Vitals analysis
- Real‑time inspection of network traffic and console errors
- Controlled browser automation in Docker‑based CI/CD pipelines
コメント