Skip to content
CAI
Software that uses CAICheck a score

ChromeDevTools/chrome-devtools-mcp

56.5

Adequate · 14 November 2026

30k

lines of production code

TypeScript

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Introduce 'slim' mode with core browser interaction tools

Adds a new 'slim' toolset in src/tools/slim/tools.ts designed for maximum token efficiency. This set includes three specific tools: 'screenshot' for capturing page images, 'navigate' for loading URLs (which now proactively handles 'beforeunload' dialogs), and 'evaluate' for running JavaScript scripts, which is gated by a 'javascriptEvaluation' condition to allow users to disable JS execution entirely. Also in this area: Improved page resizing reliability and code style updates; Script evaluation from local files and restricted file URL navigation; Slim mode tool registration and availability logic.

src/tools/slim · high confidence

Introduce background MCP daemon for persistent Chrome DevTools sessions

Users can now run the Chrome DevTools MCP server as a persistent background daemon rather than a short-lived process. A new client component (src/daemon/client.ts) manages the daemon lifecycle—starting it with configurable arguments, waiting for it to become ready via socket health checks, and stopping it—while the daemon itself (src/daemon/daemon.ts) maintains a long-running connection to the Chrome DevTools MCP tool and exposes a local socket for commands like status and tool invocation. The daemon writes a PID file with secure permissions (0o700 for the directory, 0o600 for the file) and validates ownership to prevent tampering, ensuring reliable session management across CLI interactions.

src/daemon · high confidence

Introduce chunked trace parsing and heap snapshot management

The processors module now includes a new ChunkedTraceParser that reads large Chrome DevTools trace files in batches to prevent V8 string allocation limits and heap exhaustion, alongside a new HeapSnapshotManager that enforces .heapsnapshot/.heaptimeline file extensions and manages snapshot lifecycles. These components support the new performance trace and heap snapshot analysis capabilities by providing memory-efficient parsing and structured data handling.

src/processors · high confidence

Introduce persistent config file support with live reloading

Users can now configure the Chrome DevTools MCP server via a JSON file (cd4a.config.json) discovered in predefined locations (plugin data, XDG config, or Windows AppData), eliminating the need to repeat CLI flags. The system supports a layered configuration where CLI arguments override file settings, and includes a ConfigWatcher that monitors the file for changes, allowing reloadable options (such as URL patterns, tool categories, and screenshot settings) to be updated in a running server without restarting it.

src/config · high confidence

Introduces chrome-devtools CLI and MCP server binaries with improved update checks and graceful shutdown

This change adds the executable entry points for the Chrome DevTools CLI (\chrome-devtools\) and the MCP server (\chrome-devtools-mcp\). The CLI now includes a \status\ command to check daemon health and version mismatches, and provides detailed error guidance for AI agents and developers when arguments are malformed. The MCP server binary enforces minimum Node.js LTS versions (20.19+ or 22.12+), respects the user's npm registry configuration for update checks, and ensures clean shutdown by exiting on stdin EOF and termination signals (SIGTERM/SIGINT/SIGHUP) to prevent hanging processes.

src/bin · high confidence

Introduces structured telemetry collection and reporting

The telemetry subsystem has been rebuilt to collect and report structured usage data via a dedicated watchdog process. The system now persists local state (such as last active time and last tool call) to a platform-specific JSON file, enabling daily active user tracking. It logs tool invocations with sanitized parameters, latency buckets, and context (e.g., localhost status, DevTools state), and identifies the MCP client (e.g., Claude Code, Gemini CLI, Copilot) to report usage by third-party developer tools. CLI flag usage is also recorded to track which options are explicitly set by users.

src/telemetry · high confidence

New profiling scenarios for CSS styles and console messages

The profiling tooling in scripts/profile now includes dedicated scenarios for measuring memory usage during CSS style retrieval and console message handling. The new get\_css\_styles scenario exercises the get\_css\_styles tool by navigating to a page, taking a snapshot, and repeatedly querying styles for elements with pagination, while the get\_console\_messages scenario measures the cost of navigating to a page and fetching up to 25 console messages. These scenarios allow users to profile the memory footprint of these specific MCP tool interactions. Also in this area: Daemon now runs as an MCP server instead of a client.

scripts/profile · high confidence

New profiling scenarios for console, CSS, navigation, page churn, and performance traces

Added five new profiling scenarios in scripts/profile/scenarios to exercise specific tool sets during performance measurement. The get\_console\_messages scenario iterates through console entries, get\_css\_styles retrieves styles for elements from a snapshot with pagination, navigation performs multiple page loads and captures snapshots/screenshots, page\_churn exercises page lifecycle management (open/close/list), and performance\_trace captures performance traces with explicit start/stop control. These scenarios enable targeted profiling of different browser automation patterns.

scripts/profile/scenarios · high confidence

New standalone watchdog process for reliable telemetry delivery

A new external watchdog process has been introduced to handle telemetry reporting, ensuring events are delivered even if the main application crashes. The watchdog runs as a separate process, receiving telemetry events via stdin and sending them to the Clearcut HTTP endpoint. It implements a buffering mechanism with a maximum size of 1000 events, automatic session rotation every 24 hours, and configurable flush intervals. On shutdown, it ensures a final flush of pending events before exiting, improving the reliability of telemetry data collection.

src/telemetry/watchdog · high confidence

New tooling for DevTools comments, CSS inspection, extensions, Lighthouse, memory, PWA, screencast, and third-party tools

The \src/tools\ directory has been reorganized into modular files, introducing a suite of new capabilities. Users can now interact with DevTools comments via \open\_devtools\, \get\_devtools\_comments\, \resolve\_devtools\_comment\, and \reveal\_in\_devtools\. CSS inspection is available through \get\_css\_styles\, which returns matched rules and cascade information. Chrome extension management is supported with \install\_extension\, \uninstall\_extension\, \list\_extensions\, \reload\_extension\, and \trigger\_extension\_action\. Lighthouse auditing is provided by \lighthouse\_audit\ for accessibility, SEO, and best practices. Memory debugging is expanded with \take\_heapsnapshot\, \get\_heapsnapshot\_summary\, \get\_heapsnapshot\_details\, \get\_heapsnapshot\_class\_nodes\, and \get\_heapsnapshot\_retainers\. PWA automation includes \install\_pwa\, \uninstall\_pwa\, \launch\_pwa\, and \get\_os\_app\_state\. Experimental screencast recording is available via \screencast\_start\ and \screencast\_stop\. Third-party developer tools can be listed and executed using \list\_3p\_developer\_tools\ and \execute\_3p\_developer\_tool\. Additionally, WebMCP tools are exposed through \list\_webmcp\_tools\ and \execute\_webmcp\_tool\. The tool categories have been updated to include \EXTENSIONS\, \THIRD\_PARTY\, \MEMORY\, \WEBMCP\, and \PWA\.

src/tools · high confidence

New utility infrastructure for concurrency, text handling, and URL validation

The \src/utils\ directory now includes several new modules that enhance core capabilities: \TaskRunner.ts\ introduces a concurrency system allowing independent tool calls to run in parallel while maintaining strict ordering within related queues; \text.ts\ adds safe truncation for titles and bodies that preserves surrogate pairs and emoji integrity; \url.ts\ provides robust localhost detection (including IPv4-mapped IPv6 and unspecified addresses) and strict validation for URL patterns, rejecting unenforceable constructs like partial IPv4 wildcards and named groups; \bytes.ts\ enables parsing of human-readable byte sizes and ranges; and \WaitForHelper.ts\ improves navigation and DOM stability waiting with better timeout handling and dialog management.

src/utils · high confidence

Removals

Removed legacy trace parsing and insight formatting logic

The \parse.ts\ file in \src/trace-processing\ has been deleted, removing the previous implementation for parsing raw trace buffers and formatting performance insights using the \PerformanceInsightFormatter\. This change eliminates the direct dependency on specific Chrome DevTools frontend modules for this parsing step and removes the helper function that outputted text from tool calls for development purposes.

src/trace-processing · high confidence

Architecture

Refactor browser and page management into dedicated classes

The internal architecture for managing the browser instance and per-page state has been reorganized. Browser launch and connection logic is now encapsulated in a new \BrowserManager\ class, which handles user data directories, display detection, and root-sandbox error reporting. Page-specific state (snapshots, emulation, collectors) is consolidated into a new \McpPage\ class, replacing the previous scattered Maps in \McpContext\. This refactoring also introduces a \ToolHandler\ class to manage tool execution, validation, and mutex locking, and extracts the application version into a dedicated \version.ts\ file.

src · high confidence

Behavioural changes

12 commits (5 fixes) modifying src/collectors

A change to existing behaviour in src/collectors — 12 commits (5 fixs), 3 files: “refactor: move files to folders that better represent their use (\#2564)”; “chore: add more EsLint rules (\#2885)”; “refactor: lazily initialize McpPage from Target and enumerate targets in McpContext (\#2812)”; and 9 more (refs \#2564, \#2885, \#2812, \#2888, \#2800, …).

src/collectors · medium confidence · unverified

28 commits (6 fixes) modifying src/devtools

A change to existing behaviour in src/devtools — 28 commits (6 fixs), 5 files: “build: consume devtools-frontend as a submodule (\#2481)”; “feat: add logpoints built on the DevTools BreakpointManager (\#3211)”; “chore: add more EsLint rules (\#2885)”; and 25 more (refs \#2481, \#3211, \#2885, \#3338, \#2628, …).

src/devtools · medium confidence · unverified

53 commits (0 fixes) modifying third\_party

A change to existing behaviour in third\_party — 53 commits, 1 file: “chore(deps): bump third\_party/devtools-frontend from \f7e7785\ to \7a70ee1\ (\#3235)”; “chore(deps): bump third\_party/devtools-frontend from \7da4b7e\ to \65b0ed4\ (\#2568)”; “chore(deps): bump third\_party/devtools-frontend from \f22c645\ to \daedf81\ (\#3324)”; and 50 more (refs \#3235, \#2568, \#3324, \#2886, \#2798, …).

_third\party · medium confidence · unverified

Build scripts migrate to sparse-checkout submodules and generate CLI/docs from tool definitions

The build process now initializes the devtools-frontend dependency as a sparse-checkout Git submodule (scripts/prepare.ts, scripts/clean-submodules.ts) instead of a full node\_modules package, and the post-build step (scripts/post-build.ts) creates mocks for DevTools internals (i18n, CodeMirror, skills) to support this layout. Additionally, the CLI is now auto-generated from tool schemas (scripts/generate-cli.ts), and documentation is generated directly from tool definitions (scripts/generate-docs.ts) rather than parsing runtime help output, with the README no longer being updated by the docs script.

scripts · high confidence

Chrome DevTools MCP server v1.10.1 release with ESM migration and SDK v2 upgrade

The chrome-devtools-mcp server has been updated to version 1.10.1, which includes a migration to ESM (renaming configuration files like eslint.config.mjs to eslint.config.js and .prettierrc.cjs to prettier.config.js) and an upgrade to the MCP SDK v2. The project now targets Node.js v24 (via .nvmrc) and bundles the chrome-devtools-frontend as a git submodule. This release also introduces new tools for CSS styling (get\_css\_style, get\_css\_styles), performance trace buffering, and heap snapshot querying, alongside fixes for console history retention and Puppeteer log handling.

(repo-wide) · high confidence

Lazy initialization of browser pages and new direct tool invocation API

Browser pages are now lazily initialized from Targets rather than eagerly from Puppeteer Page objects, meaning page resources (network/console collectors) are only allocated when first accessed, improving startup performance and resource usage. Additionally, the McpServer now exposes a direct callTool method that allows invoking tools by name with input validation, bypassing the standard MCP transport layer for internal or programmatic tool execution. Also in this area: 3 commits (0 fixes) modifying src; 1 commit (0 fixes) modifying src/config, src/formatters, src/third\_party; Updated Lighthouse bundle to v13.5.0; Improved resilience of service worker log collection against transient connection errors; Tool registration refactored for slim mode and title fetches made synchronous.

_src/third\party · low confidence · unverified

New ESLint rules enforce resource management, schema standards, and import safety

The project introduces several new ESLint rules in the \scripts/eslint\_rules\ directory to improve code quality and bundling safety. The \enforce-using\ rule ensures temporary file and directory helpers are declared with \using\ statements to guarantee automatic disposal, while the \enforce-zod-schema\ rule disallows \.nullable()\ and \.object()\ in tool schemas, requiring \.optional()\ and string representations instead. A new \no-direct-third-party-imports\ rule prevents value imports of third-party packages outside the \src/third\_party/\ barrel file, avoiding bundling failures. Additionally, \require-parsed-arguments\ enforces type annotations on \defineTool\ and \definePageTool\ callbacks, and the \check-license\ rule now requires an empty line after license headers.

_scripts/eslint\rules · high confidence

Replaced legacy formatter functions with new class-based formatters

The \src/formatters\ directory has been refactored to replace the previous standalone functions (found in \consoleFormatter.ts\, \networkFormatter.ts\, and \snapshotFormatter.ts\) with dedicated class-based formatters. This change introduces \CommentFormatter\, \ConsoleFormatter\, \CssFormatter\, \HeapSnapshotFormatter\, \IssueFormatter\, \NetworkFormatter\, and \SnapshotFormatter\. These new classes provide structured output capabilities via \toJSON()\ methods alongside the existing \toString()\ text formatting, and introduce new features such as CSS cascade rule analysis (including pseudo-elements, keyframes, and container queries), detailed heap snapshot context analysis, and improved network request body handling with file saving support.

src/formatters · high confidence

Test coverage

10 commits adding/updating tests in tests/collectors; 17 commits adding/updating tests in tests/devtools; 28 commits adding/updating tests in tests/e2e; Add heap snapshot test fixture; Added comprehensive test coverage for core MCP components; Added tests for DevTools comments, CSS, extensions, Lighthouse, memory, pages, and performance tools; Added tests for HeapSnapshotManager validation and caching behavior; Added tests for chunked trace parsing and trace model isolation; Added tests for config discovery, parsing, and live-reload watcher; Added tests for daemon client, utilities, and security checks; Added tests for telemetry infrastructure components; Added tests for the slim mode navigation and evaluation tools; Added unit tests for utility modules; Expanded test coverage for browser automation and evaluation scenarios; Test suite modernization and coverage updates.

Dependencies

Upgrade to MCP SDK v2 and add experimental CLI

The chrome-devtools-mcp package has been upgraded to version 1.10.1, migrating the Model Context Protocol SDK from v1 to v2 (split into @modelcontextprotocol/client, @modelcontextprotocol/core, and @modelcontextprotocol/server). This release introduces an experimental 'chrome-devtools' CLI command alongside the existing 'chrome-devtools-mcp' binary, adds Lighthouse 13.4.1 for performance auditing, and updates the supported Node.js versions to 20.19.0+, 22.12.0+, and 23+. Additionally, it includes optional peer dependencies for GCF and TOON formats, and updates dev dependencies including ESLint to v10, Puppeteer to 25.11.0, and TypeScript to v6.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.

Score

  • CAI 52 → 57 (+4.8)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 63 → 63 (+0.0)
  • Architecture 86 → 96 (+10.0)
  • Maturity 65 → 68 (+3.2)
  • Readiness 37 → 47 (+10.0)
  • Security 77 → 69 (-8.2)
  • Performance 60 → 60 (+0.0)

Resolved (26)

  • Change coupling: McpResponse.ts ↔ console.ts (src/McpResponse.ts)
  • Deprecated: sourcemap-codec (package-lock.json)
  • FunctionTooLong: post-build.main (scripts/post-build.ts)
  • FunctionTooLong: profile_mcp.profileScenario (scripts/profile/profile_mcp.ts)
  • FunctionTooLong: source_map_server.startSourceMapTestServer (scripts/profile/source_map_server.ts)
  • High CVE: [GHSA redacted] (package-lock.json)
  • Hotspot: tests/mocks.ts (tests/mocks.ts)
  • Medium: security finding (details withheld)
  • No ADRs found
  • Off-boarding risk: anonymized user #1
  • Projects may be oversized for their cohesion
  • Repeated repair: src/bin/chrome-devtools.ts (src/bin/chrome-devtools.ts)
  • Repeated repair: src/formatters/NetworkFormatter.ts (src/formatters/NetworkFormatter.ts)
  • eval_gemini.main (cognitive 16) (scripts/eval_gemini.ts)
  • generate-cli.generateCli (cognitive 24) (scripts/generate-cli.ts)
  • generate-cli.generateCli (cyclomatic 18) (scripts/generate-cli.ts)
  • generate-docs.generateConfigOptionsMarkdown (cognitive 16) (scripts/generate-docs.ts)
  • generate-docs.generateReference (cognitive 71) (scripts/generate-docs.ts)
  • generate-docs.generateReference (cyclomatic 28) (scripts/generate-docs.ts)
  • no-direct-third-party-imports-rule.discoverBundledPackages (cognitive 16) (scripts/eslint_rules/no-direct-third-party-imports-rule.js)
  • …and 6 more

New (24)

  • Change coupling: McpResponse.ts ↔ snapshot.ts (src/McpResponse.ts)
  • Hotspot: src/NetworkOverrideManager.ts (src/NetworkOverrideManager.ts)
  • Hotspot: src/formatters/NetworkFormatter.ts (src/formatters/NetworkFormatter.ts)
  • Hotspot: src/tools/script.ts (src/tools/script.ts)
  • Medium CVE: [GHSA redacted] (package-lock.json)
  • Medium CVE: [GHSA redacted] (package-lock.json)
  • Medium: security finding (details withheld)
  • Medium: security finding (details withheld)
  • Medium: security finding (details withheld)
  • Mock-dominated test: formats the errors with the DevTools universe of the handed over page (tests/McpResponse.test.ts)
  • Mock-dominated test: ignores a cached version that is not valid semver and refreshes it (tests/utils/check-for-updates.test.ts)
  • NetworkFormatter.#loadDetailedData (cyclomatic 16) (src/formatters/NetworkFormatter.ts)
  • NetworkOverrideManager.#handleRequest (cognitive 18) (src/NetworkOverrideManager.ts)
  • NetworkOverrideManager.#handleRequest (cyclomatic 17) (src/NetworkOverrideManager.ts)
  • NetworkOverridesFormatter.toString (cognitive 20) (src/formatters/NetworkOverridesFormatter.ts)
  • No ADRs found (package.json)
  • Off-boarding risk: anonymized user #1
  • Repeated repair: src/daemon/client.ts (src/daemon/client.ts)
  • lighthouse.lighthouseAudit (cognitive 16) (src/tools/lighthouse.ts)
  • performance.startTrace (cognitive 17) (src/tools/performance.ts)
  • …and 4 more

Changes since last survey

  • 78 commits — 55 feature/other, 23 fixes

By area

  • (root) — 23 commits
  • third_party/devtools-frontend — 15 commits
  • src/tools — 6 commits
  • src/utils — 6 commits
  • docs/tool-reference.md — 5 commits
  • .github/workflows — 3 commits
  • .claude-plugin/plugin.json — 2 commits
  • docs/configuration.md — 2 commits
  • src/ToolHandler.ts — 2 commits
  • src/collectors — 2 commits
  • src/third_party — 2 commits
  • docs/client-configurations.md — 1 commit
  • src/BrowserManager.ts — 1 commit
  • src/McpPage.ts — 1 commit
  • src/config — 1 commit
  • src/daemon — 1 commit
  • src/devtools — 1 commit
  • src/formatters — 1 commit
  • tests/e2e — 1 commit
  • tests/formatters — 1 commit

Notable commits

  • fix: fix(cli): reuse live daemons after EPERM (#3452)
  • fix: fix(config): accept config files with a UTF-8 BOM (#3365)
  • fix: fix(console): stop resolving a cyclic Error.cause chain after 10 causes (#3338)
  • fix: fix(extensions): say list_extensions only lists unpacked extensions (#3433)
  • fix: fix(input): validate press_key and submitKey parameters in Zod schema (#3382)
  • fix: fix(network): start an empty request list for navigations without a request (#3357)
  • fix: fix(performance): error when performance_stop_trace is called on a non-recording page (#2971) (#3117)
  • fix: fix(plugin): launch the Claude Code MCP server with npx --prefix (#3353)
  • fix: fix(tools): validate JSON object tool parameters in Zod schemas (#3383)
  • fix: fix(url): unwrap view-source: before all scheme checks in validateUrl (#3335)
  • fix: fix(wait): explain whitespace-sensitive text matching (#3350)
  • fix: fix: align root plugin.json name with marketplace entry (#3474)
  • fix: fix: disable set_logpoints when --no-javascript-evaluation is set (#3415)
  • fix: fix: ignore an invalid cached version in the update check (#3392)
  • fix: fix: keep temp files under the temp dir (#3372)
  • fix: fix: normalize non-Error values thrown by tool handlers (#3068)
  • fix: fix: preserve task serialization on request cancellation (#3079)
  • fix: fix: remove commands from claude plugin (#3469)
  • fix: fix: report page loads that keep the URL (#3395)
  • fix: fix: save binary request bodies byte for byte (#3404)
  • …and 58 more

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

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 a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 8ba2ac945ebaf1adb92208c29f3a30e73a920956 — the exact code this score is about.
  • Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-e1a3b69fc8ee.