Skip to main content
Glama
ALIEX7664

Puppeteer Debugger MCP Server

by ALIEX7664
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Puppeteer Debugger MCP Server

No user-submitted related servers found.

    Related Servers

    • Chrome Tools MCP Server

      nicholmikey
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
      29 npm
      53
      MIT

    • MCP Browser Logger

      tao-Lionel
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
      -

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      4 npm
      2
      MIT

    • DOM Analyzer MCP Server

      sudo-elia
      A
      license
      Not graded
      quality
      D
      maintenance
      A Puppeteer-based server designed for remote debugging, E2E testing, and DOM inspection of frontend applications. It allows users to interact with page elements, capture screenshots, monitor network traffic, and execute JavaScript directly within a browser environment.
      57 npm
      MIT

    • Puppeteer MCP Server

      jssyxd
      A
      license
      B
      quality
      D
      maintenance
      This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
      8
      3,224 npm
      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

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct debugging concern: memory, elements, cache, console, heap, performance, Lighthouse, navigation, screenshots, and allocations. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_memory, check_element, get_cache_status). No deviations or mixed conventions.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a debugging server. It covers essential debugging operations without being overwhelming or sparse.

    Completeness4/5

    The server covers major debugging areas: navigation, inspection, performance, memory, and console. Minor gaps like network request monitoring or DOM interaction are absent, but core debugging workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources