{"id":"benjaminr-chrome-devtools-mcp","name":"chrome-devtools-mcp","af_score":58.8,"security_score":21.5,"reliability_score":27.5,"what_it_does":"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.","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.","last_evaluated":"2026-03-30T13:34:02.322411+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"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."],"error_quality":0.0}