MCP.so
Sign In
M

MCP JS Debugger

@johngrimes

About MCP JS Debugger

Debug JavaScript and TypeScript applications through the Chrome DevTools Protocol with full source map support.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-js-debugger": {
      "command": "npx",
      "args": [
        "mcp-js-debugger"
      ]
    }
  }
}

Tools

18

Establishes a new debugging session by connecting to a Chrome DevTools Protocol (CDP) endpoint. Use this to connect to Node.js (started with --inspect), Chrome, Edge, or other CDP-compatible runtimes. Returns a session_id that must be used in all subsequent debugging operations.

Closes an active debugging session and releases all resources. Any breakpoints set in the session will be removed.

Sets a breakpoint at a specific location in the code. The breakpoint will pause execution when the specified line is reached. You can set conditional breakpoints that only trigger when an expression evaluates to true.

Removes a previously set breakpoint. Use list_breakpoints to find breakpoint IDs.

Lists all breakpoints set in a debugging session, including their locations and conditions.

Resumes execution after being paused at a breakpoint or by pause_execution. Execution continues until the next breakpoint or the program ends.

Steps over the current statement to the next line in the same function. If the current line contains a function call, the entire function executes without stepping into it. The session must be paused.

Steps into a function call if the current line contains one, otherwise steps to the next statement. Use this to examine what happens inside a function. The session must be paused.

Steps out of the current function and pauses at the calling code. Use this to quickly exit a function you've stepped into. The session must be paused.

Pauses execution at the next possible opportunity. Use this when the program is running and you want to inspect its state.

Retrieves the current call stack when execution is paused. Shows the chain of function calls that led to the current location, including function names, file locations, and scope information. If source maps are available, original source locations are included.

Evaluates a JavaScript expression in the context of a specific call frame or global context. Use this to inspect variables, test expressions, or understand the program state. The expression is evaluated in the JavaScript runtime, so you can call methods, access properties, etc.

Retrieves all variables in a specific scope. Use this to see all local variables, closure variables, or global variables at a given point in execution.

Modifies the value of a variable in a specific call frame. Use this to test different scenarios or fix values during debugging.

Configures whether the debugger should pause when exceptions are thrown. Useful for catching errors as they occur.

Maps a generated code location back to the original source location using source maps. Essential for debugging bundled or transpiled code (TypeScript, Babel, webpack, esbuild, etc.).

Retrieves the source code for a script. If source maps are available, can return the original source instead of the generated/bundled code.

Lists all scripts loaded in the debugging session. Includes source map information where available, showing which original sources are mapped.

Overview

What is MCP JS Debugger?

MCP JS Debugger is an MCP server that enables AI assistants to connect to any Chrome DevTools Protocol (CDP)-compatible debugger—such as Node.js, Chrome, or Edge—and perform full debugging operations on JavaScript and TypeScript applications. It is designed for developers who want AI-assisted debugging with breakpoints, stepping, variable inspection, and source map support.

How to use MCP JS Debugger?

Add the server using claude mcp add mcp-js-debugger -- npx mcp-js-debugger, then start your Node.js application with the --inspect-brk flag. The server automatically connects to the CDP-compatible debugger and exposes debugging tools to the AI assistant.

Key features of MCP JS Debugger

  • Set and manage breakpoints
  • Step through code (over, into, out)
  • Inspect call stacks and variables
  • Evaluate expressions in any stack frame
  • Modify variable values during execution
  • Pause on exceptions with full source map support

Use cases of MCP JS Debugger

  • Debug a Node.js backend service with AI‑guided breakpoints and variable inspection
  • Debug a browser application using Chrome or Edge DevTools Protocol
  • Debug transpiled TypeScript or bundled JavaScript while viewing original source locations
  • Integrate an AI assistant into an existing debugging workflow for step‑by‑step analysis

FAQ from MCP JS Debugger

What debuggers are compatible with MCP JS Debugger?

Any debugger that implements the Chrome DevTools Protocol, including Node.js (with --inspect), Chrome, and Edge.

How do I get started with MCP JS Debugger?

Run claude mcp add mcp-js-debugger -- npx mcp-js-debugger and then start your Node.js app with the --inspect-brk flag.

Does MCP JS Debugger support source maps?

Yes, full source map support is included, allowing you to debug TypeScript, bundled code, or any compiled JavaScript while viewing original source locations.

What runtime environment is required?

It requires Node.js and the npx command to execute the MCP server package. The debuggee (e.g., Node.js, Chrome) must be launched with CDP enabled.

How does the server transport work?

The server uses standard I/O (stdio) as the transport layer, typical for MCP servers invoked via npx or claude mcp add. There is no additional authentication mechanism described.

Frequently asked questions

What debuggers are compatible with MCP JS Debugger?

Any debugger that implements the Chrome DevTools Protocol, including Node.js (with `--inspect`), Chrome, and Edge.

How do I get started with MCP JS Debugger?

Run `claude mcp add mcp-js-debugger -- npx mcp-js-debugger` and then start your Node.js app with the `--inspect-brk` flag.

Does MCP JS Debugger support source maps?

Yes, full source map support is included, allowing you to debug TypeScript, bundled code, or any compiled JavaScript while viewing original source locations.

What runtime environment is required?

It requires Node.js and the `npx` command to execute the MCP server package. The debuggee (e.g., Node.js, Chrome) must be launched with CDP enabled.

How does the server transport work?

The server uses standard I/O (stdio) as the transport layer, typical for MCP servers invoked via `npx` or `claude mcp add`. There is no additional authentication mechanism described.

Comments

More Other MCP servers