Chrome DevTools MCP — Connect & Self-Heal the WSL→Windows Bridge

imboard-ai/devtools/chrome-devtools-connect v1.0.1 risk: medium signed Draft

Objective: Get the chrome-devtools MCP driving a real Windows Chrome from a WSL2 session — launch the browser if needed, diagnose and repair the debug-port bridge (Chrome 149+ binds ::1 only; a stale portproxy strands it), then verify end-to-end control with navigate + screenshot.

Use it

Inspect metadata

ai-dossier info imboard-ai/devtools/chrome-devtools-connect

Download to the current directory

ai-dossier pull imboard-ai/devtools/chrome-devtools-connect

Verify, then run

ai-dossier run imboard-ai/devtools/chrome-devtools-connect

Needs the CLI.

Trust and risk

Declared risk level	medium (network_access, system_configuration, executes_external_code)
Requires approval	no
Checksum	`sha256:332be9aa7a58eca011cf6c00fe19155b103218081b20fe81d6ec9e541cb6ae75`
Signature	ed25519, key `imboard-ai` by Yuval Dimnik <yuval.dimnik@gmail.com>
Signed at	2026-07-26T12:46:44.259Z (covers frontmatter+body)
Public key	`m97FPrnq/zKlQArLvJl3bTZCUMWWpp/d0UJ/OfUKZeE=`

These values are copied from the published dossier header. This site does not verify them: run ai-dossier verify before trusting a dossier.

Details

Categories	devops
Tags	chrome-devtools, mcp, wsl2, browser-automation, portproxy, live-verify, setup
Tools required	curl, powershell.exe, chrome-devtools MCP
Authors	Yuval Dimnik
Source	raw `.ds.md`