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.

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.tsreaches 172 of 293 modules (59%) within 2 hops; 109 modules depend on it directly.
Summary
| Modules | 293 |
| Dependencies between modules | 919 |
| Functions, constants, classes and types | 1,316 |
| Languages | ts 276, js 17 |
| Boundary violations | 0 |
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.
| File | Direct dependents | Within 2 hops |
|---|---|---|
src/third_party/index.ts | 109 | 172 |
src/tools/ToolDefinition.ts | 42 | 88 |
src/config/mcp-options.ts | 37 | 119 |
scripts/eval_gemini.ts | 32 | 32 |
src/utils/logger.ts | 30 | 84 |
src/tools/categories.ts | 30 | 75 |
src/types.ts | 18 | 87 |
src/McpContext.ts | 14 | 74 |
src/config/ServerConfig.ts | 14 | 67 |
src/TextSnapshot.ts | 14 | 61 |
src/third_party/cli.ts | 12 | 132 |
src/utils/TaskRunner.ts | 12 | 79 |
src/McpResponse.ts | 12 | 71 |
src/processors/HeapSnapshotManager.ts | 11 | 111 |
src/McpPage.ts | 11 | 86 |
Where to start reading
Files that nothing else depends on and that pull in the most modules:
src/daemon/daemon.ts, depends on 13 modulessrc/bin/chrome-devtools.ts, depends on 12 modulesscripts/generate-cli.ts, depends on 7 modulesscripts/generate-docs.ts, depends on 6 modulesscripts/update_metrics.ts, depends on 6 modulesscripts/profile/profile_mcp.ts, depends on 4 modulessrc/telemetry/watchdog/main.ts, depends on 3 modulesscripts/profile/scenarios/get_css_styles.ts, depends on 2 modulesscripts/profile/scenarios/page_churn.ts, depends on 2 moduleseslint.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.
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)