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

@oussamaexe/electron-debugger

v3.0.0

Published

MCP server for debugging Electron apps via Chrome DevTools Protocol

Readme

electron-debugger

Status: Work in progress. APIs and tool set are evolving. Not published to npm yet — only installable from source.

MCP server for debugging Electron apps via Chrome DevTools Protocol (CDP).

Prerequisites

Your Electron app must be running with remote debugging:

/path/to/your-electron-app --remote-debugging-port=9222

Installation

npm install -g electron-debugger

Or run directly:

npx electron-debugger mcp

Configuration

| Variable | Default | Description | |---|---|---| | ELECTRON_DEBUG_PORT | 9222 | CDP debugging port | | ELECTRON_DEBUG_HOST | 127.0.0.1 | Debugging host address |

Usage

MCP Server

electron-debugger mcp

For opencode, add to opencode.json:

{
  "mcpServers": {
    "electron-debugger": {
      "command": "npx",
      "args": ["electron-debugger", "mcp"]
    }
  }
}

CLI

electron-debugger exec get-dom-snapshot depth=3
electron-debugger exec click-element selector=button.submit
electron-debugger exec take-screenshot format=png

Available Tools

| Tool | Description | |---|---| | get-dom-snapshot | Get DOM tree snapshot | | get-element-box | Get bounding box for a CSS selector | | get-element-styles | Get computed styles | | take-screenshot | Capture page or element screenshot | | get-console-logs | Retrieve console entries | | get-metrics | Get performance metrics (FPS, memory, DOM nodes) | | click-element | Click an element by CSS selector | | type-text | Type text into an input field | | highlight-element | Visually highlight an element | | list-windows | List all open BrowserWindows |

1. The Big Picture — What This Thing Does

Big Picture

2. How It Connects — The Plumbing

How It Connects

How It Works

  1. Electron app exposes a CDP WebSocket via --remote-debugging-port
  2. electron-debugger discovers page targets at http://127.0.0.1:9222/json
  3. Connects to the first page target via WebSocket
  4. Tools communicate using Chrome DevTools Protocol commands
  5. MCP server exposes these as tool definitions for AI assistants

Development

git clone https://github.com/oussamaexe/electron-debugger.git
cd electron-debugger
npm install
npm run build
npm test

License

MIT