Skip to main content
Glama
johngrimes

MCP JS Debugger

by johngrimes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP JS Debugger

No user-submitted related servers found.

    Related Servers

    • chrome-debugger-mcp

      BitePro
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to attach to Chrome tabs, set breakpoints, inspect scope variables, evaluate expressions, and step through code using Chrome DevTools Protocol for runtime debugging.
      18
      30 npm
      1
      MIT

    • cdp-tools-mcp

      InDate
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to debug code and automate browsers using Chrome DevTools Protocol, supporting breakpoints, variable inspection, and replayable interaction recording.
      35
      389 npm
      16
      MIT

    • MCP Debugger

      debugmcp
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to perform step-through debugging of Python, JavaScript/Node.js, and Rust programs using the Debug Adapter Protocol, with support for breakpoints, variable inspection, and stack traces.
      21
      166
      MIT

    • CDP-MCP Server

      jekyll-001
      F
      license
      Not graded
      quality
      D
      maintenance
      Wraps Chrome DevTools Protocol to provide AI agents with low-level browser debugging tools including breakpoints, stack traces, stepping, network interception, and source maps.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool maps to a distinct debugging operation—session lifecycle, breakpoint management, stepping, execution control, state inspection, and source mapping—so there is no meaningful overlap between tools. Even similar stepping tools are clearly differentiated by whether they step over, into, or out of function calls.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun pattern using clear, predictable verbs like connect, disconnect, set, remove, list, get, resume, pause, step, and evaluate. This makes the toolset easy to navigate and anticipate.

    Tool Count4/5

    At 18 tools, the server is slightly above the typical 3–15 sweet spot, but the count is well justified for a debugger covering session management, breakpoints, stepping, inspection, and source maps. The tools are organized around the complete debugging workflow rather than being redundant.

    Completeness5/5

    The toolset covers the full debugging lifecycle: connect/disconnect sessions, breakpoint CRUD, execution control, call stack and scope inspection, variable mutation, exception handling, and source map support. There are no obvious dead ends or missing operations for standard JavaScript debugging via CDP.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources