Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Chrome DevTools MCPMCP100 Recommended | Codebase Memory MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation io.github.ChromeDevTools · Publisher source ↗ | First-party MCP DeusData · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Sep 24, 2026 Package: Sep 21, 2026 | Repo: Aug 14, 2026 Package: Aug 14, 2026 |
| Popularity evidence | ||
| GitHub stars | 52,542 GitHub stars · checked 2026-09-24T04:14:16.273000Z | 44,904 GitHub stars · checked 2026-09-25T18:35:00Z |
| Package downloads / 30 days | 7,881,886 package downloads / 30 days · checked 2026-09-24T04:17:39.032000Z | 28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | No server authentication is documented for local stdio. Running-browser connections support optional WebSocket headers; an open remote-debugging port lets local applications control Chrome. | local stdio; no remote auth needed |
| Cost | The open-source npm package lists no MCP fee. Chrome, Node.js, client, model, and external-service costs are separate. | none beyond local resources |
| Permissions | Inspects, debugs, automates, and modifies browser state through navigation, input, script evaluation, screenshots, uploads, extensions, memory, performance, and PWA tools. | reads indexed source/project data; installer writes supported agent/editor configs/hooks |
| Data handling | Browser content is exposed to the connected client. Performance tools send trace URLs to Google CrUX by default, and usage statistics with invocation success, latency, and environment data are enabled by default; broader retention is not documented. | local processing; current docs state no source/index/query/env/telemetry upload |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Can expose sensitive browser sessions and execute arbitrary browser actions or scripts. Use isolated profiles, URL allow/block patterns, restricted file paths, and do not expose remote-debugging ports. | latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-09-23 |
| Candidate evidence | 2026-09-24T04:25:05.554391Z | 2026-09-25T18:35:00Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →