Skip to main content
Glama
Himangguo

chrome-devtools-mcp

by Himangguo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to chrome-devtools-mcp

No user-submitted related servers found.

    Related Servers

    • Chrome DevTools MCP

      khawjaahmad
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automated debugging, performance analysis, and web interaction. It leverages Puppeteer and Chrome DevTools to provide capabilities like network monitoring, console logging, and automated browser actions.
      -

    • 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,500,288 npm
      Apache 2.0

    • DevTools Lens MCP

      aakcay5656
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.
      19
      2 npm
      MIT

    • 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
      47 npm
      1
      MIT
    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

    A3.8/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of browser inspection: layout, tabs, DOM query, DOM tree, ancestors, styles, box model, JS execution, console, and network. Even the two style-related tools (computed vs. matched) are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, list_, query_, evaluate_), making the API predictable and easy to reason about. No mixed conventions or vague verbs.

    Tool Count5/5

    11 tools is well-scoped for a browser debugging server. Each tool covers a distinct capability without unnecessary overlap, and the count feels appropriate for the intended breadth.

    Completeness4/5

    The surface covers DOM, CSS, layout, JS evaluation, console, and network inspection, which are core for debugging. Missing interaction features (e.g., click, navigate, modify styles) suggest a read-only inspector, but that's consistent with the tool descriptions; minor gaps like screenshots or performance tracking could be added.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources