Privacy and advertising choices
Git-Stars uses essential storage for site operation. Optional analytics and ad-measurement scripts stay disabled unless you accept them; partners such as Google may then use cookies or similar identifiers where required. Privacy Policy
Chrome DevTools for coding agents
This repository page has enough original analysis, source evidence, and comparison context to be treated as an indexable Git-Stars review.
100
review score
Problem solved
It solves the problem of AI agents lacking direct, reliable access to browser internals for debugging and automation. Unlike traditional approaches that rely on limited APIs or screenshots, this provides full DevTools capabilities (network, console, performance traces) with source-mapped stack traces and automatic waiting for action results.
Deployment reality
The available setup signal starts with: npx -y chrome-devtools-mcp@latest. Treat this as a starting point, then ask Codex or Claude to inspect the README, environment variables, runtime version, and deployment target before production use.
Commercial use
The recorded license is Apache-2.0. This is a useful commercial-use signal, but teams should still verify license text, dependencies, model/API terms, and trademark constraints.
Capability ceiling
Developers can build AI-powered debugging assistants that record performance traces, analyze network requests, take screenshots, and inspect console messages in real time. Real-world use cases include automated performance regression detection, intelligent error reproduction, and AI-driven end-to-end testing. The ceiling is limited only by what Chrome DevTools can do—essentially full browser introspection and control.
Git-Stars is independent and not affiliated with GitHub or this project. Analysis may be AI-assisted and based on public repository metadata plus short README-derived summaries. We do not mirror full README files, docs, issues, or social comments.
ChromeDevTools/chrome-devtools-mcp is tracked as a TypeScript project in the AI Agent, MCP Server, Developer Tool, Infrastructure area. This evaluation combines public GitHub metadata, category signals, short source summaries, and Git-Stars editorial rules rather than copying project documentation.
Momentum check: the repository has 49k total stars, with +69 today, +0 this week, and +0 this month. These growth windows help distinguish durable adoption from short-lived visibility spikes.
Maintenance check: current activity is Active; the latest push was 9 days ago, and the open issue queue is 111, about 0.23% of total stars. Treat this as an adoption signal, not a substitute for engineering due diligence.
Adoption check: 3.4k forks and 49k watchers suggest how often the project is reused or followed. License signal: Apache-2.0. Always verify license compatibility before commercial or internal use.
Practical fit: this project is most relevant when you need TypeScript teams evaluating ecosystem-native tooling. Be cautious when you need a legal review, security audit, or production SLA.
Source check: Git-Stars currently has 2 explicit source reference(s) for this report and a recent growth signal of 1.1k. Follow the original GitHub repository for final install, security, and release information.
Analysis
ReadyOriginal problem, capability, and verdict guidance are available.
Sources
ReadyRepository metadata and README/source references are attached.
License
ReadyApache-2.0 is recorded for review.
Maintenance
ReadyRecent activity is visible in repository metadata.
Alternatives
ReadyEnough nearby projects exist for comparison.
Momentum
49k Stars
Reuse
3.4k Forks
Attention
49k Watchers
Maintenance
active
License
Apache-2.0
Open issues
111
Chrome DevTools for agents (chrome-devtools-mcp) is an MCP server that lets AI coding assistants control and inspect a live Chrome browser, providing access to Chrome DevTools for automation, debugging, and performance analysis.
Key Features
- Get performance insights using Chrome DevTools traces and actionable data. - Advanced browser debugging: analyze network requests, take screenshots, and check console messages with source-mapped stack traces. - Reliable automation via Puppeteer with automatic waiting for action results.
AI Agent
Agent frameworks, autonomous workflows, and tool-use systems
MCP Server
Model Context Protocol servers, clients, and integrations
Developer Tool
Tools that improve coding, testing, build, and local workflow
Infrastructure
Cloud, deployment, networking, containers, and platform tooling
npx -y chrome-devtools-mcp@latest80
Health Score
Active
Commit Activity
Sep 11, 2025
Created
Aug 13, 2026
Last push
+772
Today's growth
+1.1k
7-day growth
+1.1k
30-day growth
Forks
Open
Watchers
ChromeDevTools
GitHub profilecodecrafters-io/build-your-own-x
Master programming by recreating your favorite technologies from scratch.
freeCodeCamp/freeCodeCamp
freeCodeCamp.org's open-source codebase and curriculum. Learn math, programming, and computer science for free.
nilbuild/developer-roadmap
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
awesome-selfhosted/awesome-selfhosted
A list of Free Software network services and web applications which can be hosted on your own servers
practical-tutorials/project-based-learning
Curated list of project-based tutorials
✓
License
✓
Forked
✓ Active
Maintained
Problem Solved
It solves the problem of AI agents lacking direct, reliable access to browser internals for debugging and automation. Unlike traditional approaches that rely on limited APIs or screenshots, this provides full DevTools capabilities (network, console, performance traces) with source-mapped stack traces and automatic waiting for action results.
Capabilities
Developers can build AI-powered debugging assistants that record performance traces, analyze network requests, take screenshots, and inspect console messages in real time. Real-world use cases include automated performance regression detection, intelligent error reproduction, and AI-driven end-to-end testing. The ceiling is limited only by what Chrome DevTools can do—essentially full browser introspection and control.
Bottom Line
This tool is ideal for developers building AI coding agents that need deep browser debugging and automation capabilities. It should be avoided if you require support for non-Chrome browsers or are uncomfortable with default usage statistics collection. The key trade-off is powerful browser control versus privacy considerations and Chrome-only support.