How to run chrome mcp under WSL ?

Resolved 💬 3 comments Opened Nov 2, 2025 by it-sha Closed Mar 29, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

We have a workaround solution for Claude Code https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/131#issuecomment-3417555953

But do we have some working solution with Codex CLI ?

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#5166
#4400

Powered by Codex Action

dbalabka · 7 months ago

So, I ended up with a shell script that checks and applies all required Windows settings and then starts already installed Windows Chrome with the proper configuration:
https://github.com/dbalabka/chrome-wsl/

You can simply start Chrome (the initial run may require applying some Windows tweaks):

npx @dbalabka/chrome-wsl

To stop Chrome:

npx @dbalabka/chrome-wsl --stop

To completely clean up the applied Windows settings:

npx @dbalabka/chrome-wsl --uninstall

If you want to run the agent inside a Docker container, you can ask the script to apply the required adjustments inside the container as well:

npx @dbalabka/chrome-wsl --container=<name>

To setup to DevTools MCP you need the following settings:

[mcp_servers.chome-devtools]
command = "npx"
args = ["-y", "chrome-devtools-mcp@latest", "--browser-url=http://127.0.0.1:9222"]
startup_timeout_sec = 20.0

etraut-openai contributor · 5 months ago

This bug report hasn't received any upvotes or additional posts in three months. Closing.