$ loading_
Debug web apps through Chrome DevTools using natural language commands.
This MCP tool declares no required secrets or fixed remote endpoints, and its source is auditable, with no clear high-risk red flags evident from the materials. The main concerns are its inherent local execution and access to browser debugging data, so it is best used with an isolated browser profile.
The materials explicitly state that no keys or environment variables are required, and there is no indication of API keys, account tokens, or other sensitive credentials; credential exposure appears low.
No fixed remote endpoint is declared, and there is no evidence that the tool itself sends data to third-party services; however, its Chrome DevTools connection, network monitoring, and debugging functions may expose web request/response data during use.
The system flags it as executes-code; based on the description, it likely interacts locally with Chrome/DevTools, which is standard MCP-style local execution and debugging control and should be treated accordingly.
The description indicates network monitoring, console inspection, and performance analysis, implying access to console output, performance data, and related session content for the pages being debugged. The materials do not show broad filesystem access or clearly excessive permissions beyond the stated purpose.
Positive factors are that it is open source under the MIT License and therefore theoretically auditable; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and is a fork, so community validation and maintenance signals are weak.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-devtools-mcp-fork" yet — see the docs or source repo.
Connect to the currently open Chrome page, inspect console errors and warnings, organize them by severity, and explain likely causes and fixes for each issue.
A console issue report with error summaries, likely causes, impact, and recommended fixes.
Use Chrome DevTools to analyze this page's loading and runtime performance, identify the slowest requests, scripts, or rendering stages, and provide optimization priorities.
A performance analysis showing key bottlenecks, supporting metrics, and actionable optimization recommendations.
Monitor network requests during page load, identify failed, timed-out, or abnormal-status API calls, and summarize request parameters, response details, and likely issues.
A network diagnostics report listing problematic endpoints, error patterns, and troubleshooting directions.
Control a real Chrome browser for browsing, interaction, and page reading.
Control Chrome for debugging, automation, and performance analysis via DevTools.
Connect Chrome DevTools so AI can debug pages and inspect performance.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.
Connect Chrome DevTools to help AI agents debug and inspect web pages.
Control and inspect live Chrome for automation, debugging, and performance analysis.