43
/ 100
9 days ago
glama

wsl-chrome-mcp-bridge

A bridge to launch Chrome on Windows from WSL2 and proxy Chrome DevTools MCP tools. It enables browser automation via Claude Code in WSL2 by managing Chrome's lifecycle and exposing debugging capabilities.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configCHROME_DEBUG_PORTport, -p 9222 Chrome remote debugging port
configCHROME_HEADLESSheadless =1 off Run Chrome in headless mode
configCHROME_PATHchrome-path auto-detect Path to Chrome executable
configCHROME_USER_DATA_DIRuser-data-dir C:\tmp\chrome-devtools-mcp Chrome user data directory (Windows path)
configNPX_PATH
configSYSTEMROOT
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 1 concrete improvement we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/dijdzv-wsl-chrome-mcp-bridge-jy237i)](https://m8ven.ai/mcp/dijdzv-wsl-chrome-mcp-bridge-jy237i)
commit: f1d80eae49e6804162281196457f5b5755d7fde3
code hash: 12d1f03dc653a5a95f346ea61e7321393aad0a3f6f9822c1247c9076723a79b3
verified: 7/22/2026, 8:41:37 AM
view raw JSON →