chrome-devtools-mcp
Provides an MCP server that bridges Claude Desktop/Claude Code to the Chrome DevTools Protocol (CDP), enabling LLM-driven browser debugging such as starting/connecting to Chrome, navigating pages, inspecting DOM and JS objects, monitoring network traffic and console output, and collecting performance/storage data.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The tool can start/connect to Chrome with remote debugging and can access sensitive browser data (cookies, storage) and execute JavaScript. No auth/scoping model is described, so rely on local-only use and network isolation. TLS cannot be meaningfully assessed for local MCP/CDP connections from the provided README. Dependency list includes websockets/aiohttp; specific CVE status is unknown from the provided content.
⚡ Reliability
Best When
When an operator is using Claude Desktop/Claude Code to debug a web application locally in Chrome with remote debugging enabled, and needs conversational access to CDP capabilities (network/console/DOM/performance/storage).
Avoid When
Avoid exposing the server or remote debugging port to untrusted networks; avoid using in sensitive environments without controls because it can read cookies/storage and execute JavaScript in a live browser context.
Use Cases
- • Debugging web app network requests (failed API calls, response inspection)
- • Investigating JavaScript console errors and warnings
- • Inspecting runtime JS objects/variables and executing JavaScript in the browser context
- • Analyzing page performance and resource loading metrics
- • Inspecting and manipulating page/DOM state (element attributes, HTML, layout, search)
- • Inspecting and managing browser storage (cookies, localStorage/sessionStorage, IndexedDB)
- • Monitoring console output and events in real time during debugging sessions
Not For
- • Running as a general-purpose remote browser automation service for production workloads
- • Environments where you cannot run Chrome/Chromium with remote debugging enabled
- • Use cases requiring strict privacy/least-privilege around cookie/session access without additional isolation controls
- • Unauthenticated internet-exposed deployments (it is intended to be used locally via MCP clients/desktop)
Interface
Authentication
No authentication mechanism is described. Access is effectively controlled by the MCP client/desktop configuration and the local Chrome remote debugging port.
Pricing
No pricing information in provided materials; repository appears open-source (MIT).
Agent Metadata
Known Gotchas
- ⚠ Requires a Chrome instance with remote debugging enabled (e.g., CHROME_DEBUG_PORT).
- ⚠ Path/venv issues are a common failure mode for Claude Code CLI; absolute paths to interpreter and server are recommended.
- ⚠ Operations are stateful (starting Chrome, navigating pages, clearing storage/cookies), so repeated calls may have side effects.
- ⚠ No explicit guidance provided here on rate limiting, timeouts, or recovery semantics for MCP calls.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for chrome-devtools-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.