Node Debugger

Created By
qckfxa year ago
Overview

what is Node Debugger?

Node Debugger is an MCP server that provides debugging capabilities for Node.js applications, allowing for efficient process management and debugging of AI agents.

how to use Node Debugger?

To use Node Debugger, install the server, configure it with your project or globally, and utilize the provided tools in Claude Code for managing and debugging Node.js processes.

key features of Node Debugger?

  • Process management for starting/stopping Node.js processes with debugging enabled.
  • Debugging tools for setting breakpoints, stepping through code, and evaluating expressions.
  • Integration with Node.js Inspector API for real debugging sessions.
  • Designed for long-running debugging sessions, making it AI agent friendly.

use cases of Node Debugger?

  1. Debugging complex Node.js applications in real-time.
  2. Managing multiple debugging sessions for different applications.
  3. Assisting AI agents in debugging their processes effectively.

FAQ from Node Debugger?

  • Can Node Debugger handle multiple processes?

Yes! It allows you to manage and debug multiple Node.js processes simultaneously.

  • Is Node Debugger easy to set up?

Yes! Follow the installation steps to configure it for project-specific or global use.

  • What debugging features does Node Debugger offer?

It offers breakpoints, code stepping, expression evaluation, and more for effective debugging.

Server Config

{
  "mcpServers": {
    "debugger-mcp": {
      "type": "stdio",
      "command": "node",
      "args": [
        "build/index.js"
      ],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qckfx
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago