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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@_brcode/mcp-browser-inspector

v1.1.3

Published

MCP server for browser inspection with Puppeteer - network monitoring and console error tracking

Readme

Browser Inspector MCP Server

npm version npm downloads GitHub

Puppeteer-based MCP server for browser inspection, network monitoring, and console error tracking.


📦 Installation (2 simple steps)

Step 1: Install the package globally

Open your terminal and run:

npm install -g @_brcode/mcp-browser-inspector

This installs the package globally on your system. You only need to do this once.

Step 2: Add to Claude Code MCP

After installation, add the MCP server to Claude Code:

claude mcp add --scope user --transport stdio browser-inspector npx @_brcode/mcp-browser-inspector

That's it! ✅ The MCP server is now ready to use in Claude Code.

Verify installation

Check if the server is connected:

claude mcp list

You should see:

browser-inspector: npx @_brcode/mcp-browser-inspector - ✓ Connected

💡 What you need

  • Node.js (version 18 or higher)
  • Claude Code CLI installed

Don't have Claude Code CLI? Install it from here.


🎯 Quick Usage

Once installed, you can use these commands in Claude Code:

# Inspect a website
inspect_url https://example.com

# View all API requests
get_api_requests

# View network traffic
get_network_data

# Check console errors
get_console_errors

# Close browser
close_browser

🖥️ Using with Claude Desktop

If you're using Claude Desktop instead of Claude Code CLI, follow these steps:

Step 1: Install the package globally

npm install -g @_brcode/mcp-browser-inspector

Step 2: Configure Claude Desktop

Edit your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Linux: ~/.config/Claude/claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "browser-inspector": {
      "command": "npx",
      "args": ["@_brcode/mcp-browser-inspector"]
    }
  }
}

If you already have other MCP servers configured, just add the browser-inspector entry to your existing mcpServers object.

Step 3: Restart Claude Desktop

Close and reopen Claude Desktop for the changes to take effect.

Verify installation

After restart, you should see the browser-inspector tools available in Claude Desktop. Try asking Claude to:

  • "Inspect https://example.com"
  • "Show me the API requests"
  • "Check for console errors"