Skip to directory

About Node.js Debugger

Connects Claude Code to Node.js's Inspector Protocol for real-time debugging capabilities, enabling breakpoint setting, variable inspection, and code execution stepping without leaving the conversation interface.

What you can use it for

  • developer tools
Connection and setup
Hosting
Local stdio process
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No credentials were configured; the tested read-only tool “inspect_variables” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

  • Node.js 18+
  • The public install config and runtime call passed; package/profile repository links differ and are recorded for review.

Setup steps

  1. npx -y @hyperdrive-eng/mcp-nodejs-debugger@0.2.2
Tools 13+

Repository was archived 2026-01-09; existing 13 tool rows not independently reconciled from README.

  • nodejs_inspect

    Executes JavaScript code in the debugged process

    Parameters: js_code
    01
  • set_breakpoint

    Sets a breakpoint at specified line and file

    Parameters: file, line
    02
  • inspect_variables

    Inspects variables in current scope

    Parameters: scope
    03
  • step_over

    Steps over to the next line of code

    04
  • step_into

    Steps into function calls

    05
  • step_out

    Steps out of current function

    06
  • continue

    Continues code execution

    07
  • delete_breakpoint

    Deletes a specified breakpoint

    Parameters: breakpointId
    08
  • list_breakpoints

    Lists all active breakpoints

    09
  • evaluate

    Evaluates a JavaScript expression in the current context

    Parameters: expression
    10
  • get_location

    Gets the current execution location when paused

    11
  • get_console_output

    Gets the most recent console output from the debugged process

    Parameters: limit
    12
  • retry_connect

    Manually triggers a reconnection attempt to the Node.js debugger

    Parameters: port
    13

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Runtime verification covered one read-only tool call (inspect_variables); other listed tools were not individually exercised.
  • The profile repository documents the @hyperdrive-eng/mcp-nodejs-debugger package, while npm metadata points to the package-maintainer repository; both are retained for review.
  • {}
Source discrepancies
  • The profile repository documents the @hyperdrive-eng/mcp-nodejs-debugger package, while npm metadata points to the package-maintainer repository; both are retained for review.
Original sources
  • MCP.Directory public profile

    Name, description, publisher identifier, categories, transport, tool inventory, and install configuration.

  • Linked publisher repository

    Repository URL linked from the public profile; any npm repository difference is recorded separately.

  • npm-declared package repository

    The profile repository documents the @hyperdrive-eng/mcp-nodejs-debugger package, while npm metadata points to the package-maintainer repository; both are retained for review.

  • npm registry metadata

    Published package version 0.2.2 checked before launch. Registry repository: git+https://github.com/hyperdrive-eng/mcp-nodejs-debugger.git. The profile repository documents the @hyperdrive-eng/mcp-nodejs-debugger package, while npm metadata points to the package-maintainer repository; both are retained for review.

  • maintainer repository documentation

    Maintainer repository matches the catalog package, but it is archived and README does not provide a canonical complete tool count in the retrieved sections.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.