ChromeDevTools/chrome-devtools-mcp
This system is a Chrome DevTools MCP server that provides programmatic access to browser debugging and performance analysis capabilities. It enables users to manage browser contexts, capture and analyze heap snapshots, run Lighthouse audits, and execute JavaScript on web pages. The architecture features a persistent daemon process for reliable background operation, structured telemetry logging, and a CLI interface for automation and evaluation.
69.0
Adequate · 3 August 2026
32k
lines of production code
TypeScript
with JavaScript
3
bus factor · 114 authors in all
3
measurements over time
How it got here
2025 · Release 1.6.0 and tooling expansion
This period centered on the release of version 1.6.0, which introduced new capabilities for memory debugging, Chrome extension management, and Lighthouse integration. The codebase underwent significant refactoring to improve modularity, with formatters and context management reorganized into dedicated classes. Comprehensive test coverage was added for the new tools and existing components, supported by updated dependencies and automated CLI generation scripts.
14 changes
2026 · Daemon architecture and telemetry infrastructure
This period focused on transitioning the application to a persistent daemon architecture to improve startup times and enable background operation. Concurrently, significant effort was invested in the telemetry subsystem, introducing a dedicated watchdog process for reliable, asynchronous logging. The scope also included expanding tooling capabilities for browser automation and memory leak debugging, supported by comprehensive test coverage for all new features.
14 changes
Survey your own repository
ChromeDevTools/chrome-devtools-mcp was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit c5ebf9e202 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.