$ loading_
Connect Chrome DevTools to help AI agents debug and inspect web pages.
This is an open-source Chrome DevTools MCP with very high community adoption, requiring no secrets and declaring no remote endpoints, so overall risk appears low. Its main capabilities are likely local browser/devtools interaction, which is normal for this class of tool, but local execution and browser data access boundaries still warrant attention.
The materials explicitly state that no keys or environment variables are required, and there is no request for API tokens, account credentials, or third-party authorization, resulting in low credential exposure.
The materials declare no remote endpoints, and there is no indication of sending user data to external services. Based on the available facts, it appears to operate through a local debugging path; any later website access would be normal browser behavior rather than an additional exfiltration red flag shown in the materials.
The system checks indicate executes-code capability, meaning it may start local processes or invoke a local browser/debugging components. This is a normal capability for an MCP tool and not, by itself, a high-risk signal, but it should still be run in a controlled environment.
From the name and description, its functionality centers on Chrome DevTools, which typically involves access to browser page content, debugging information, and related local session data. The materials do not show excessive system-level permissions beyond the stated purpose, but sensitive data within browser contexts still deserves attention.
The source is an open-source GitHub repository under Apache-2.0 with very strong community adoption (about 43k stars), all of which are significant positive signals. The sparse README and unknown maintenance status create some audit blind spots, but not enough to outweigh the source credibility.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-devtools-mcp" yet — see the docs or source repo.
Use Chrome DevTools to inspect the current page console and network requests, identify the JavaScript error causing the blank page, and suggest fixes.
A report with the root error, related request status, and actionable frontend fixes.
Analyze this page’s loading performance with Chrome DevTools, identify the main reasons for slow initial render, and provide a prioritized optimization list.
Performance bottlenecks with optimization recommendations ranked by priority.
Use Chrome DevTools to inspect the API requests triggered by form submission and summarize the URL, method, parameters, response, and any anomalies.
A concise API request summary for reproducing issues or collaborating with backend engineers.
Control and inspect live Chrome for automation, debugging, and performance analysis.
Control Chrome for debugging, automation, and performance analysis via DevTools.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.
Develop, debug, and troubleshoot Next.js projects inside an AI coding agent.
Let multiple AI agents concurrently control and inspect a live Chrome browser.
Control and debug running Node.js processes through a CDP-to-DAP bridge.