$ loading_
Connect AI to Chrome tabs for inspection, debugging, and runtime diagnostics.
This MCP tool claims to connect to a local running Chrome tab via the Chrome DevTools Protocol for debugging and page inspection. It does not declare secrets or remote endpoints, so overall risk is not high, but caution is warranted because it can execute locally and access browser page data. Open source and ISC licensing are positive signals, while low adoption and unknown maintenance limit supply-chain confidence.
The materials explicitly state that no keys or environment variables are required, and there is no request for API tokens, account credentials, or other secrets; based on the provided facts, credential exposure appears low.
No remote endpoint is declared, and the description indicates it mainly connects to a locally running Chrome tab via CDP. However, browser pages themselves may interact with external sites, and the tool may access page content and network context during inspection/debugging, so users should watch for any undocumented data egress in the actual implementation.
The system flags it as executes-code, and as an MCP server it would normally run locally and interact with Chrome's debugging interface. This is a standard capability for this type of tool; the materials do not show privilege requests beyond the stated purpose, but it should be treated as having local execution and browser automation/debugging capabilities.
Per the description, it supports runtime debugging and page inspection, so it can access content in the current Chrome tab, including DOM, runtime script state, and possibly debugging data. The materials do not indicate broad filesystem permissions, but access to browser-context data itself warrants caution.
The project is open source with an ISC license, making the code in principle auditable, which is a clear risk-reducing factor. However, it comes from a third-party registry, shows only 0 stars, and has unknown maintenance status, so trust and maturity are limited; code and dependencies should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-dev-mcp" yet — see the docs or source repo.
Connect to the currently open Chrome tab, inspect console errors, failed network requests, and script exceptions, then tell me the root cause and suggested fixes.
A report with console errors, failed request details, root-cause analysis, and actionable fixes.
Connect to this Chrome page and inspect why the login button is not clickable by analyzing the DOM, styles, overlays, and event bindings.
An element state analysis explaining why it is unclickable, with recommended changes.
Connect to the running Chrome tab, inspect key requests, resource sizes, and performance bottlenecks during page load, then summarize optimization opportunities.
A page-load performance diagnosis including bottleneck resources, suspicious requests, and optimization recommendations.
Connect Chrome DevTools so AI can debug pages and inspect performance.
Control Chrome for debugging, automation, and performance analysis via DevTools.
Control a real Chrome browser for browsing, interaction, and page reading.
Automate Chromium for web actions, debugging, and browser testing tasks.
Control and inspect live Chrome for automation, debugging, and performance analysis.
Connect Chrome DevTools to help AI agents debug and inspect web pages.