npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

wsl-chrome-mcp-bridge

v0.2.0

Published

MCP bridge that launches Chrome on Windows from WSL2 and proxies chrome-devtools-mcp

Readme

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 tools

The 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.

Requirements

  • WSL2 with mirrored networking mode enabled (see below)
  • Node.js >= 20
  • Google Chrome installed on Windows
  • npx available 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=mirrored

Then 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-bridge

Claude Code configuration

Add to your .mcp.json:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "wsl-chrome-mcp-bridge"]
    }
  }
}

Options

| Option | Environment Variable | Default | Description | |--------|---------------------|---------|-------------| | --port, -p | CHROME_DEBUG_PORT | 9222 | Chrome remote debugging port | | --user-data-dir | CHROME_USER_DATA_DIR | C:\tmp\chrome-devtools-mcp | Chrome user data directory (Windows path) | | --chrome-path | CHROME_PATH | auto-detect | Path to Chrome executable | | --headless | CHROME_HEADLESS=1 | off | Run Chrome in headless mode | | --help, -h | | | Show help | | --version, -v | | | Show version |

Chrome path auto-detection

  1. Query Windows registry via PowerShell (App Paths\chrome.exe)
  2. Check known paths (/mnt/c/Program Files/Google/Chrome/Application/chrome.exe, etc.)

License

MIT