MCP Node.js Debugger

Created By
hyperdrive-enga year ago
✸ MCP Node.js debugger
Overview

What is MCP NodeJS Debugger?

MCP NodeJS Debugger is a tool that allows developers to debug NodeJS applications at runtime using the Claude Code environment.

How to use MCP NodeJS Debugger?

To use the MCP NodeJS Debugger, you need to add it to Claude Code, start your NodeJS server in debug mode, and then ask Claude Code to help you debug any runtime errors.

Key features of MCP NodeJS Debugger?

  • Runtime debugging of NodeJS applications
  • Integration with Claude Code for enhanced debugging capabilities
  • Ability to set breakpoints and inspect variables during execution

Use cases of MCP NodeJS Debugger?

  1. Debugging runtime errors in NodeJS applications.
  2. Inspecting variable states and application flow during execution.
  3. Assisting in resolving database connection issues in real-time.

FAQ from MCP NodeJS Debugger?

  • Can MCP NodeJS Debugger help with all NodeJS applications?

Yes! It is designed to work with any NodeJS application running in debug mode.

  • Is there a cost to use MCP NodeJS Debugger?

No! It is free to use within the Claude Code environment.

  • How do I remove the debugger from Claude Code?

You can remove it by running the command: claude remove nodejs-debugger.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hyperdrive-eng
Star
107
Language
JavaScript
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