Chrome DevTools for coding agents
INTEGRATE — Add immediately via one JSON config snippet; this is the official Google/ChromeDevTools MCP server giving any AI coding agent full Chrome DevTools access for debugging, automation, and performance tracing.
23/24 — actively-maintained / well-documented / high-discipline
Failed: H8: FAIL — README contains only an npm version badge; no CI badge (GitHub Actions, Travis, CircleCI) or explicit .github/workflows/ reference appears in the provided README or manifest data.
Passed: H1: PASS — latest release chrome-devtools-mcp-v0.26.0 tagged 2026-05-12. H2: PASS — release 6 days ago, well within 12 months. H3: PASS — last commit 2026-05-18 (today), 0 days ago. H4: PASS — last commit 2026-05-18, same day as appraisal. H5: PASS — archived: false. H6: PASS — 73 open issues, within the healthy 1–99 range signalling active triage. H7: PASS — Apache-2.0 license explicitly declared.
Failed: none.
Passed: D1: PASS — README is present and non-empty. D2: PASS — README far exceeds 1000 bytes; extensive multi-section content with MCP client configs for 10+ clients. D3: PASS — "Getting started" section provides verbatim npx install JSON config. D4: PASS — multiple code blocks appear under "Getting started" and per-client headers. D5: PASS — README links to Tool reference and Slim tool reference. D6: PASS — first paragraph states "lets your coding agent…control and inspect a live Chrome browser" within 150 characters. D7: PASS — links to docs/cli.md, docs/troubleshooting.md, docs/design-principles.md, and CHANGELOG.md. D8: PASS — "Disclaimers" section explicitly states browser support caveats, data-sharing warnings, and usage statistics defaults.
Failed: none.
Passed: E1: PASS — primary language is TypeScript. E2: PASS — package.json present with full manifest. E3: PASS — no runtime "dependencies" field; package is fully bundled via rollup so end-user install carries 0 production deps. E4: PASS — package.json has "test": "npm run build && node scripts/test.mjs"; scripts/test.mjs referenced throughout. E5: PASS — 39,891 stars, far above the 50-star threshold. E6: PASS — ~8.2 months old, 39,891 stars ≈ 4,865 stars/month vs. the 2/month threshold. E7: PASS — 2,542 forks, well above the 5-fork threshold. E8: PASS — description "Chrome DevTools for coding agents" is meaningful and >20 characters.
| Dimension | Score | Assessment |
|---|---|---|
| Harvest Value | 2 | Novel MCP server architecture from Google that exposes Chrome DevTools primitives (performance traces, source-mapped stack traces, CrUX field data, Puppeteer automation) as MCP tools — directly harvestable patterns for designing PAI's own tool interfaces. |
| Integration Readiness | 2 | Single JSON config snippet and npx -y chrome-devtools-mcp@latest is all that's required; detailed setup guides exist for Claude Code, Cursor, Copilot, Cline, Codex, and 6 other clients the vault owner may already use. |
| Overlap Risk | 1 | Partial overlap with Hacker-Valley-Media--Interceptor (AI Agent Browser Control, NOTE verdict, 3.7/24) — both expose browser control to agents, but chrome-devtools-mcp adds DevTools-specific debugging, performance tracing, slim mode, and source maps that Interceptor lacks. |
| Gap Fill | 2 | Directly addresses the declared landscape gap: "AI Agent Browser Control: only Hacker-Valley-Media--Interceptor — needs alternatives for comparison"; chrome-devtools-mcp is a dramatically stronger alternative (39,891 vs. implied low stars) and fills the category with a production-ready option. |
Composite: 0.88
Category: MCP Browser DevTools Crowding: 0 repos in vault (first-in-category) Alternatives: first in this category; nearest neighbor in vault is Hacker-Valley-Media--Interceptor under secondary category AI Agent Browser Control (NOTE, 3.7/24) vs. top alternative: chrome-devtools-mcp dwarfs Interceptor in adoption (39,891 vs. low stars), maintenance (daily commits), and depth (DevTools performance tracing, source maps, slim mode vs. basic interception) Landscape impact: filling a gap — establishes the MCP Browser DevTools category and provides a strong second entry for AI Agent Browser Control, addressing an explicit landscape gap
Density: 10/10 — all 10 evidence inputs available: repo metadata (stars, forks, dates, license, archived status), README (first 8KB, substantive and multi-section), dependency manifest (full package.json with scripts, devDependencies, engines), topics/tags list, latest release info, language, description, open issue count, landscape context with categories and gaps, related prior appraisals (5 entries for cross-reference).
The package bundles all runtime dependencies (puppeteer, lighthouse, @modelcontextprotocol/sdk) via rollup into the distributable, which is why devDependencies (34 entries) includes what would normally be production deps — the published npm package ships with zero runtime dependencies. This is an intentional architecture choice for reliability and is reflected in the bundle script. The Google-authored provenance, Apache-2.0 license, and --no-usage-statistics opt-out flag make it suitable for privacy-conscious vault use.