wsl-chrome-mcp-bridge
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wsl-chrome-mcp-bridge Open Chrome and navigate to https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
wsl-chrome-mcp-bridge
MCP bridge that launches Chrome on Windows from WSL2 and proxies chrome-devtools-mcp.
How it works
Claude Code (WSL2)
↕ stdio (JSON-RPC)
wsl-chrome-mcp-bridge (WSL2)
├── spawns Chrome on Windows (--remote-debugging-port)
├── spawns chrome-devtools-mcp via npx
└── proxies MCP messages + adds chrome_open / chrome_close toolsThe bridge adds two lifecycle tools (chrome_open / chrome_close) and proxies all other tool calls to chrome-devtools-mcp. Chrome is launched on-demand when chrome_open is called and tool definitions are prefetched at startup for instant availability.
Related MCP server: chrome-local-mcp
Requirements
WSL2 with mirrored networking mode enabled (see below)
Node.js >= 20
Google Chrome installed on Windows
npxavailable in PATH
WSL2 mirrored networking
The bridge connects to Chrome's debug port at 127.0.0.1. WSL2's default NAT mode isolates the network from Windows, so mirrored mode is required.
Add to %USERPROFILE%\.wslconfig:
[wsl2]
networkingMode=mirroredThen restart WSL: wsl --shutdown
Installation
# Run directly (no install needed)
npx -y wsl-chrome-mcp-bridge
# Or install globally
npm install -g wsl-chrome-mcp-bridgeClaude Code configuration
Add to your .mcp.json:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "wsl-chrome-mcp-bridge"]
}
}
}Options
Option | Environment Variable | Default | Description |
|
|
| Chrome remote debugging port |
|
|
| Chrome user data directory (Windows path) |
|
| auto-detect | Path to Chrome executable |
|
| off | Run Chrome in headless mode |
| Show help | ||
| Show version |
Chrome path auto-detection
Query Windows registry via PowerShell (
App Paths\chrome.exe)Check known paths (
/mnt/c/Program Files/Google/Chrome/Application/chrome.exe, etc.)
License
MIT
Available Tools
2 toolschrome_closeA
Close the Chrome debugging instance and disconnect DevTools MCP.
Inputs: no named parameters.
chrome_openA
Launch Chrome with remote debugging and connect DevTools MCP. Call this before using any other Chrome DevTools tools.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools, chrome_open and chrome_close, are completely distinct actions with no overlap. Each serves a single clear purpose.
Both tools follow the consistent pattern 'chrome_<verb>', using snake_case and clear verb_noun structure.
With exactly two tools for opening and closing the bridge, the count is minimal but perfectly scoped for the server's intended role.
The tool set fully covers the lifecycle of the Chrome debugging instance (start and stop), with no necessary operations missing for this narrow domain.
Related MCP Connectors
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.316MIT
- AlicenseNot gradedqualityDmaintenanceLightweight MCP server for controlling a Windows Chrome instance from WSL, designed for AI coding agents with minimal token overhead and human-in-the-loop support.MIT
- AlicenseNot gradedqualityDmaintenanceLocal browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.1MIT
- AlicenseNot gradedqualityCmaintenanceRuns chrome-devtools-mcp on the Windows side so AI agents inside WSL can drive Windows-side Chrome despite its loopback-only DevTools endpoint, auto-detecting all paths with no configuration. Enables agents to navigate pages, click, fill forms, execute JavaScript, read the accessibility tree, and take screenshots from WSL.MIT