Skip to main content
Glama
BitePro

chrome-debugger-mcp

by BitePro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-debugger-mcp

No user-submitted related servers found.

    Related Servers

    • cdp-tools-mcp

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

    • MCP JS Debugger

      johngrimes
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to debug JavaScript and TypeScript applications by connecting to Chrome DevTools Protocol-compatible debuggers, allowing them to set breakpoints, step through code, inspect variables, and evaluate expressions with full source map support.
      18
      10
      2
      Apache 2.0

    • Chrome DevTools MCP

      Anirbandz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.
      1,516,489
      Apache 2.0

    • 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
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation3/5

    Core tools are distinct, but waitForPause vs waitForSpecificPause have heavily overlapping blocking-wait semantics that could easily cause misselection. getScopeVariables vs evaluate also blur boundaries, and startDebuggingSession's auto-trigger instructions create confusion about when the workflow tool is appropriate.

    Naming Consistency4/5

    Consistently camelCase with mostly verb-first names, and the stepInto/stepOver/stepOut family is clean. Minor deviations: 'evaluate' and 'resume' are bare verbs without a resource prefix, and the verb vocabulary is somewhat varied (launch, list, connect, set, force, reload), but no convention mixing.

    Tool Count3/5

    18 tools is in the heavy range, and several could be consolidated (waitForPause/waitForSpecificPause, getStatus overlapping with wait functionality, startDebuggingSession being more of a workflow document than a tool). Not egregiously bloated—each tool does meaningful work—but the set could be trimmed to ~14-15 without losing expressiveness.

    Completeness4/5

    Covers the full debug lifecycle: launch, connect, breakpoints, pause, inspect, step, resume, and status. Minor gaps: no way to list active breakpoints, and the workflow skips STEP 4 entirely. Exception handling is only mentioned tangentially in waitForPause. Otherwise, a well-covered surface that achieves its debugging purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources