ChromeDevTools/chrome-devtools-mcp

Prefer this fork if you want a customized agent-bridge workflow with longer waits, cross-discussion, and extra orchestration features. Prefer upstream if you want the latest Chrome DevTools MCP fixes, better compatibility, and lower maintenance risk.

Choose this fork only if its custom workflow or simplification is the point. For most adopters, upstream is the safer default because this fork is significantly behind and appears to have trimmed major bundled tooling.

Choose this fork only if you want the extra agent/workflow scaffolding and are willing to own a large merge and maintenance burden. If you mainly want Chrome DevTools MCP itself, upstream looks safer and more current.

Prefer this fork only if you need its older compatibility or onboarding tweaks. For most adopters, upstream is the better choice because it is far more current and has recent feature and bugfix work this fork lacks.

Choose this fork if Brave support is the main requirement. Choose upstream if you want the latest MCP behavior, faster fixes, and lower maintenance risk.

Choose upstream unless you specifically need this fork's namespace or a frozen copy. This fork shows no added capabilities and is behind current upstream, so adopters mainly inherit the same product with recent improvements missing.

Choose this fork if your priority is remote-browser deployment and custom MCP configuration. Choose upstream if you want the newest fixes, lower maintenance burden, and the most validated performance/debugging path.

Choose this fork if you want a customized MCP server with extra in-page tool visibility and are comfortable owning compatibility and update risk. Choose upstream if you want the latest fixes, tighter browser support, and lower maintenance overhead.

Choose this fork only if stealth or specialized browser workflows matter more than staying aligned with upstream. For most adopters who want a maintained Chrome DevTools MCP server with the latest fixes, upstream is the safer choice.