Skip to main content
Glama
SHAY5555-gif

Chrome DevTools MCP

by SHAY5555-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Chrome DevTools MCP

No user-submitted related servers found.

    Related Servers

    • chrome-devtools-mcp

      zhang77-X
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.
      3,204,746 npm
      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.
      3,204,746 npm
      Apache 2.0

    • Chrome DevTools MCP

      dinesh-nalla-se
      A
      license
      Not graded
      quality
      D
      maintenance
      Lets AI coding assistants control and inspect a live Chrome browser using full Chrome DevTools capabilities for browser automation, debugging, and performance analysis.
      3,204,746 npm
      Apache 2.0

    • 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.
      -
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.5/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between 'navigate_page' and 'navigate_page_history' that could cause confusion. The descriptions clarify that 'navigate_page' goes to a URL while 'navigate_page_history' handles back/forward navigation, but the naming doesn't make this distinction obvious. Other tools like 'fill' and 'fill_form' are well-differentiated by scope.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., 'click', 'close_page', 'drag') with clear, descriptive names. There are minor deviations like 'performance_analyze_insight' which uses a verb_verb_noun structure, but overall the pattern is predictable and readable across the set.

    Tool Count3/5

    With 26 tools, the count is borderline high for a DevTools server, potentially feeling heavy but still manageable. It covers a broad range of browser automation tasks, which justifies the number, but it might overwhelm agents with too many options for basic operations.

    Completeness5/5

    The toolset provides comprehensive coverage for browser automation and DevTools functionality, including navigation, interaction, performance analysis, network monitoring, and debugging. There are no obvious gaps; it supports full lifecycle operations from page creation to performance tracing and element manipulation.

    Resources