May 13, 2026
12 min readYour MCP Chrome DevTools Bridge Isn't Broken. Your Port Proxy Is Pointing At The Wrong Address Family.
Driving Chrome from inside WSL2 via MCP DevTools fails when your netsh portproxy rule points at the wrong address family. The fix is one netstat check away — but the Microsoft docs (and the AI tools that learned from them) get it wrong half the time.
By Sean O'Dea