Chrome DevTools MCP: a map of its code, package by package.

Chrome DevTools MCP is the MCP server that gives coding agents Chrome DevTools. Wingbox built the graph of the repository, with no model, and the map stacks its code by package: 151 files and 468 dependencies on 14 planes, the packages the others depend on lower. Click a file to see what a change to it reaches.

Chrome DevTools MCP on 14 package planes, one file selected with its blast radius
Open the live mapRead the reportChromeDevTools/chrome-devtools-mcpDrag to turn the planes, scroll to zoom, click a file for its blast radius.
The report

What Wingbox wrote on the whole repository

REPORT.md as the tool wrote it, without its own guesses of architecture layers.

Wingbox report: chrome-devtools-mcp

Generated on 2026-11-16 by wingbox 0.2.6 from the code graph of this project. Open map.html in this folder for the interactive map.

Key findings

  • A change to src/third_party/index.ts reaches 172 of 293 modules (59%) within 2 hops; 109 modules depend on it directly.

Summary

Modules293
Dependencies between modules919
Functions, constants, classes and types1,316
Languagests 276, js 17
Boundary violations0

Most depended-on modules

A change in one of these files reaches the most code (test files are left out). "Within 2 hops" counts the modules that depend on it directly or through one other module.

FileDirect dependentsWithin 2 hops
src/third_party/index.ts109172
src/tools/ToolDefinition.ts4288
src/config/mcp-options.ts37119
scripts/eval_gemini.ts3232
src/utils/logger.ts3084
src/tools/categories.ts3075
src/types.ts1887
src/McpContext.ts1474
src/config/ServerConfig.ts1467
src/TextSnapshot.ts1461
src/third_party/cli.ts12132
src/utils/TaskRunner.ts1279
src/McpResponse.ts1271
src/processors/HeapSnapshotManager.ts11111
src/McpPage.ts1186

Where to start reading

Files that nothing else depends on and that pull in the most modules:

  • src/daemon/daemon.ts, depends on 13 modules
  • src/bin/chrome-devtools.ts, depends on 12 modules
  • scripts/generate-cli.ts, depends on 7 modules
  • scripts/generate-docs.ts, depends on 6 modules
  • scripts/update_metrics.ts, depends on 6 modules
  • scripts/profile/profile_mcp.ts, depends on 4 modules
  • src/telemetry/watchdog/main.ts, depends on 3 modules
  • scripts/profile/scenarios/get_css_styles.ts, depends on 2 modules
  • scripts/profile/scenarios/page_churn.ts, depends on 2 modules
  • eslint.config.js, depends on 1 module

Next steps

Check what a change will reach before you make it:

wingbox impact src/third_party/index.ts

Rebuild after the code changes with wingbox build. This report and the map are rewritten on every build.

Limits

The graph comes from static parsing. Dependencies created at run time (dependency injection, reflection, generated code) are not visible here.

Method

How this was made

  • Wingbox 0.2.6 from PyPI on the whole repository at commit 86a1c23, 2026-11-16: one command, wingbox build .
  • The map leaves out the 142 test files and puts every other file on the plane of its package, the folder of its nearest package manifest. The planes are stacked by the dependencies between packages.
  • Checked against the code. TypeScript and JavaScript dependencies compared with an import resolver written apart from Wingbox: 919 in the graph, 900 found by the resolver, 900 in both. The more in the graph are imports of the compiled output (out/Default/gen/...) that Wingbox maps back to their source through tsconfig outDir and rootDir.

Run it on any repository: pipx install wingbox && wingbox build . · Wingbox on GitHub (MIT)