Skip to main content
Glama
Sign In
MCP NodeJS Debugger

MCP NodeJS Debugger

by workbackai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP NodeJS Debugger

No user-submitted related servers found.

    Related Servers

    • node-runtime

      keiththornton
      A
      license
      A
      quality
      C
      maintenance
      Gives Claude Code a live Node.js debugger over the V8 Inspector protocol, letting it launch or attach to a running process, set conditional breakpoints, step through execution, inspect scopes and stack frames, evaluate expressions in a frame, and read stdout/stderr — with no instrumentation added to the code.
      20
      MIT

    • Node.js Debugger MCP

      ScriptedAlchemy
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to debug Node.js applications using Chrome DevTools Protocol. Provides comprehensive debugging capabilities including breakpoints, stepping, variable inspection, expression evaluation, and console monitoring.
      5,984 npm
      350
      MIT

    • claude-debugs-for-you

      jasonjmcghee
      A
      license
      Not graded
      quality
      D
      maintenance
      Enable Claude (or any other LLM) to interactively debug your code (set breakpoints and evaluate expressions in stack frame). It's language-agnostic, assuming debugger console support and valid launch.json for debugging in VSCode.
      16 npm
      514
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'evaluate' and 'nodejs_inspect' both execute code, causing potential confusion. The stepping and breakpoint tools are clearly differentiated.

    Naming Consistency3/5

    Naming mixes conventions: 'continue' is a verb alone, 'nodejs_inspect' is noun_verb, and 'retry_connect' is verb_verb. Most others follow verb_noun, but inconsistency lowers clarity.

    Tool Count5/5

    13 tools cover essential debugging actions—breakpoints, stepping, inspection, evaluation, and connection—without being excessive or sparse for the domain.

    Completeness4/5

    Core debugging workflows are covered, but missing features like call stack inspection, watch variables, and conditional/exception breakpoints create minor gaps.

    Resources