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

@remenby/chromium-mcp

v0.2.0

Published

MCP server for Chromium/Chrome browser automation - Fork of Browser MCP with Chrome launcher

Downloads

3

Readme

About

Chromium MCP is a fork of Browser MCP that adds support for automatically launching Chrome/Chromium with the Browser MCP extension loaded.

This MCP server + Chrome extension allows you to automate your browser using AI applications like VS Code, Claude, Cursor, and Windsurf.

What's New in This Fork

🚀 Chrome Launcher Tool

This fork adds a new launch_browser tool that automatically:

  • Launches Chrome with your specified profile
  • Loads the Browser MCP extension
  • Waits for the extension to connect
  • Returns when ready to receive commands

No more manual setup! Just call the tool and start automating.

Features

  • Fast: Automation happens locally on your machine, resulting in better performance without network latency.
  • 🔒 Private: Since automation happens locally, your browser activity stays on your device and isn't sent to remote servers.
  • 👤 Logged In: Uses your existing browser profile, keeping you logged into all your services.
  • 🥷🏼 Stealth: Avoids basic bot detection and CAPTCHAs by using your real browser fingerprint.
  • 🚀 Auto-Launch: NEW! Automatically launch Chrome with the extension loaded.

Installation

NPM Package (Recommended)

npm install -g @remenby/chromium-mcp

Or use with npx:

{
  "mcpServers": {
    "chromium-mcp": {
      "command": "npx",
      "args": ["@remenby/chromium-mcp@latest"]
    }
  }
}

From Source

git clone https://github.com/Remenby31/chromium-mcp.git
cd chromium-mcp
npm install
npm run build

Usage

With Claude Desktop / MCP-compatible clients

Add to your MCP configuration file:

For Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "chromium-mcp": {
      "command": "npx",
      "args": ["@remenby/chromium-mcp@latest"]
    }
  }
}

Using the Chrome Launcher

Once connected to the MCP server, you can use the new launch_browser tool:

launch_browser with:
- extensionPath: "/path/to/browser-mcp-extension"
- url: "https://example.com" (optional)
- profilePath: "/path/to/chrome/profile" (optional)

The tool will:

  1. Launch Chrome with the extension loaded
  2. Wait for the extension to connect (default: 30 seconds timeout)
  3. Return success when ready

Requirements:

  • The Browser MCP extension must be unpacked (not a .crx file)
  • The extension should be configured to auto-connect, or you must click "Connect" within the timeout period

Available Tools

Navigation

  • browser_navigate - Navigate to a URL
  • browser_go_back - Go back in browser history
  • browser_go_forward - Go forward in browser history

Interaction

  • browser_snapshot - Capture an accessibility tree snapshot of the page
  • browser_click - Click on an element
  • browser_hover - Hover over an element
  • browser_type - Type text into an element
  • browser_select_option - Select an option in a dropdown
  • browser_press_key - Press a keyboard key

Utility

  • browser_wait - Wait for a specified time
  • browser_get_console_logs - Get console logs from the browser
  • browser_screenshot - Take a screenshot of the current page
  • launch_browser - NEW! Launch Chrome with the Browser MCP extension

Configuration

The default WebSocket port is 9333. You can change this in src/config/mcp.config.ts.

Differences from Original

This fork is fully standalone and doesn't depend on the monorepo packages. All necessary code has been extracted and included locally:

  • Configuration (@repo/configsrc/config)
  • Types (@repo/typessrc/types)
  • Messaging (@r2r/messagingsrc/messaging)
  • Utils (@repo/utilssrc/utils)

Development

# Install dependencies
npm install

# Build the project
npm run build

# Type check
npm run typecheck

# Watch mode
npm run watch

Publishing to NPM

  1. Login to npm:
npm login
  1. Update version in package.json

  2. Build and publish:

npm run build
npm publish --access public

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

This is a fork of Browser MCP. For the original project, see BrowserMCP/mcp.

Credits

License

Apache 2.0 - See LICENSE file for details