Skip to main content
This guide explains how to set up the Chrome DevTools MCP server so Claude Code can inspect and control your Chrome browser.

​
Linux

​
1. Start Chrome with remote debugging

​
2. Install Claude Code

​
3. Add the Chrome DevTools MCP

Make sure the port in --browserUrl matches the --remote-debugging-port you used when launching Chrome.

​
Windows + WSL

​
1. Configure WSL mirrored networking

Create a file called .wslconfig in your Windows user profile directory (%USERPROFILE%, e.g. C:\Users\YourName\.wslconfig) with the following content:
Important: The file must be named exactly .wslconfig — not .wslconfig.txt. If you created it with Notepad, double-check that it didn’t append .txt to the filename.
After creating or editing the file, restart WSL:

​
2. Install Claude Code and add the MCP (inside WSL)

Open your WSL terminal and run:

​
3. Start Chrome on Windows

Open cmd or PowerShell on Windows and run:
The port must match the one you used in the --browserUrl flag above.

​
Verify the connection

​
1. Check the debug endpoint

Open your browser and navigate to:
You should see a JSON response like this:
If you see this, the debug protocol is active.

​
2. Check the MCP connection in Claude Code

Inside Claude Code, run:
You should see chrome-devtools listed as a connected MCP server. If it appears with a green status, Claude can communicate with your browser.

​
Devcontainer

The devcontainer is already configured to set up the Chrome DevTools MCP automatically. The postCreateCommand in .devcontainer/devcontainer.json installs dependencies and registers the MCP server, resolving the host IP via host.docker.internal:
All you need to do is:
  1. Start Chrome on your host machine with --remote-debugging-port=4222 (see the Linux or Windows sections above).
  2. Inside the devcontainer, verify the MCP is registered by running /mcp in Claude Code.