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

@dubaigit/bdg-mcp

v1.0.1

Published

MCP server for browser debugging via Chrome DevTools Protocol using bdg

Readme

@dubaigit/bdg-mcp

MCP (Model Context Protocol) server for browser debugging via Chrome DevTools Protocol (CDP).

Key feature: Connect to remote Chrome browsers with API key authentication - works with Fly.io, AWS, or any cloud-hosted Chrome instance.

Installation

npm install -g @dubaigit/bdg-mcp

Add to Claude Code

claude mcp add bdg-mcp -- npx -y @dubaigit/bdg-mcp

Or manually add to ~/.claude.json:

{
  "mcpServers": {
    "bdg-mcp": {
      "command": "npx",
      "args": ["-y", "@dubaigit/bdg-mcp"]
    }
  }
}

Available Tools

| Tool | Description | |------|-------------| | connect_browser | Connect to remote Chrome via WebSocket URL with API key auth | | disconnect_browser | Disconnect from current session | | browser_status | Check connection status | | navigate | Navigate to a URL | | screenshot | Capture page screenshot (png/jpeg/webp, full page support) | | evaluate | Execute JavaScript in page context | | get_page_content | Get full HTML of current page | | get_page_info | Get URL and title | | query_selector | Find elements by CSS selector | | click | Click on element | | type_text | Type text into input fields | | cdp | Execute raw CDP commands | | reload | Reload page | | go_back / go_forward | Browser history navigation |

Usage Example

  1. Connect to a remote Chrome browser:
connect_browser with wsUrl: "wss://your-chrome.fly.dev:9226/devtools/page/PAGE_ID?apiKey=YOUR_API_KEY"
  1. Navigate and interact:
navigate to "https://example.com"
screenshot
get_page_info
  1. Execute JavaScript:
evaluate expression: "document.title"
  1. Raw CDP commands:
cdp method: "Page.printToPDF" params: { printBackground: true }

Remote Chrome Setup

This MCP server is designed to work with remote Chrome browsers. You can set up a remote Chrome with CDP proxy using:

  • Fly.io: Deploy Chrome in a Docker container with a CDP proxy that handles API key authentication
  • Your own infrastructure: Any Chrome instance with --remote-debugging-port exposed

Example WebSocket URL format:

wss://hostname:port/devtools/page/PAGE_ID?apiKey=YOUR_API_KEY

License

MIT