Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams using Claude, Cursor, Copilot, or other coding agents on web apps: wire it into a non-sensitive browser profile first, then use it to reproduce UI bugs, inspect console errors, and collect performance traces during agent-assisted debugging.
Who should use it
Who should skip it
Skip ChromeDevTools/chrome-devtools-mcp if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
ChromeDevTools/chrome-devtools-mcp is tracked by RepoRadar as a developer tool in the Developer Tools section. First seen 2026-06-16; the source record was last checked on 2026-06-16. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for ChromeDevTools/chrome-devtools-mcp are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The ChromeDevTools/chrome-devtools-mcp record combines a 8.6/10 composite score with separate popularity (88.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
can inspect live browser sessions; may expose cookies, page data, screenshots, or private network traffic if connected to a sensitive profile.