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

chrome-mcp-router

v0.3.1

Published

A resilient MCP proxy for Chrome DevTools that provides automatic reconnection on crash and project-based port resolution

Readme

chrome-mcp-router

A proxy wrapper for chrome-devtools-mcp that adds auto-reconnect and project-based configuration.

  • Auto-reconnect: Detects Chrome crashes and automatically restarts the child process when Chrome comes back up
  • Project routing: Resolve Chrome debug URLs by project name instead of specifying port numbers directly

Installation

# Run with npx (no installation required)
npx -y chrome-mcp-router@latest --project myproject

Usage

.mcp.json configuration

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-mcp-router@latest", "--project", "myproject"]
    }
  }
}

CLI Options

chrome-mcp-router --project <name>
chrome-mcp-router --browserUrl <url>

| Option | Description | | --- | --- | | --project <name> | Resolve browserUrl by project name from the config file | | --browserUrl <url> | Specify Chrome debug URL directly (e.g. http://127.0.0.1:9222) |

Other flags (--slim, --no-usage-statistics, etc.) are passed through to chrome-devtools-mcp.

Config file

Specify project name to URL mappings in ~/.config/chrome-mcp-router/config.json.

{
  "projects": {
    "myproject": {
      "browserUrl": "http://127.0.0.1:9200"
    },
    "anotherproject": {
      "browserUrl": "http://127.0.0.1:9201"
    }
  }
}

How it works

  1. If --project is specified, resolves browserUrl by project name from the config file
  2. Starts chrome-devtools-mcp as a child process and bidirectionally proxies stdio
  3. Polls Chrome's /json/version endpoint every 3 seconds to check liveness
  4. When it detects that Chrome has restarted after a crash, stops the old child process, starts a new one, and transparently restores the session by replaying the MCP handshake

License

MIT