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

mcp-debug-unit

v0.3.11

Published

Model Context Protocol server exposing a debug-script tool for Node.js inspector sessions.

Readme

mcp-debug-unit

MCP server that gives coding agents the ability to debug Node.js and Python scripts without modifying source code.

Published on npm as mcp-debug-unit (formerly nodejs-debug-mcp). The legacy CLI alias remains available for backwards compatibility.

Why install this

Your coding agent (Claude, Cursor, etc.) can inspect runtime values without modifying your code. Instead of asking the agent to add console.log statements, it can call debug-script to see what's happening at any line during execution.

Particularly useful for debugging unit tests and helping agents write tests by understanding what values are actually present at runtime.

How it works

The agent specifies:

  • A Node.js command to run
  • A breakpoint location (file and line)
  • An expression to evaluate

The tool runs the script, pauses at that line each time it executes, evaluates the expression, and returns all values when the script finishes.

Parameters

  • command: Debuggable command to run. For Node.js pass --inspect-brk, for Python run under debugpy with --listen + --wait-for-client.
  • breakpoint: { file: string, line: number }
  • expression: Expression to evaluate when the breakpoint is hit. Works for both runtimes.
  • timeout: Maximum execution time in milliseconds
  • includeStack: (optional) Include call stack frames in the result
  • runtime: (optional) 'node' (default) or 'python'

Setup

Claude Code

claude mcp add --scope user --transport stdio mcp-debug-unit -- npx -y mcp-debug-unit

Codex CLI

codex mcp add mcp-debug-unit -- npx -y mcp-debug-unit

Cursor

Add to your MCP settings config file:

{
  "mcpServers": {
    "mcp-debug-unit": {
      "command": "npx",
      "args": ["-y", "mcp-debug-unit"]
    }
  }
}

Development

npx tsc                        # Build
node --test test/e2e.test.js  # Test

Python runtime requirements

  • Install debugpy (e.g. python3 -m pip install debugpy)
  • The MCP server bootstraps debugpy automatically into your user cache (e.g. ~/.cache/mcp-debug-unit/debugpy/<hash> or %LOCALAPPDATA%\mcp-debug-unit\cache\debugpy\<hash>) if the interpreter referenced in your command cannot import it. Override the storage location via MCP_DEBUG_UNIT_DEBUGPY_DIR (or the legacy NODEJS_DEBUG_MCP_DEBUGPY_DIR).
  • Launch your script via python3 -m debugpy --listen 127.0.0.1:5678 --wait-for-client ./script.py
  • Call debug-script with runtime: "python" and the same listen host:port in the command
  • Use absolute or relative paths for the breakpoint.file (they will be resolved automatically)

See SPECIFICATION.md for implementation details.

Release

To publish a new version to npm:

# Patch version (0.1.2 → 0.1.3)
npm version patch && git push --follow-tags

# Minor version (0.1.2 → 0.2.0)
npm version minor && git push --follow-tags

# Major version (0.1.2 → 1.0.0)
npm version major && git push --follow-tags

This automatically:

  • Updates package.json version
  • Creates a git commit and tag
  • Pushes to GitHub
  • Triggers the publish workflow

License

MIT