Skip to main content
Glama
MahyarNemati

cdp-extended-mcp

by MahyarNemati
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cdp-extended-mcp

No user-submitted related servers found.

    Related Servers

    • argus

      Jmsa
      A
      license
      Not graded
      quality
      D
      maintenance
      Chrome DevTools Protocol MCP server for browser debugging with tools for console, network, screenshots, and DOM interaction.
      5 npm
      MIT

    • 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

    • 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

    • Puppeteer Debugger MCP Server

      ALIEX7664
      A
      license
      B
      quality
      C
      maintenance
      An MCP server based on Puppeteer and Chrome DevTools Protocol for advanced browser debugging, performance analysis, and memory detection. It enables users to inspect DOM elements, monitor console errors, capture screenshots, and perform heap snapshot analysis through persistent browser connections.
      10
      15 npm
      1
      MIT

    • js-reverse-mcp

      1600822305
      A
      license
      Not graded
      quality
      D
      maintenance
      A Chrome DevTools Protocol-based MCP server that enables AI coding assistants to control browsers for JavaScript debugging, reverse engineering, web scraping, and API debugging.
      690 npm
      1
      Apache 2.0
    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 40 tools

    Disambiguation5/5

    Every tool targets a distinct feature or action within its category. The fetch_* set covers interception stages clearly, and emulation tools each address a separate emulation dimension. Even overlapping-looking tools like css_background_colors and css_computed_style are clearly differentiated by their specific purpose.

    Naming Consistency5/5

    All tool names use lowercase snake_case and follow a predictable pattern: either verb_noun (e.g., connect_cdp, discover_targets) or a category prefix followed by a descriptive noun or verb (e.g., emulate_device, css_coverage_stop). The naming is highly consistent across the entire set of 40 tools.

    Tool Count2/5

    40 tools is well above the typical well-scoped range of 3-15. While the broad CDP domain might justify a larger surface, this many tools can overwhelm agents and increase selection difficulty. The count feels excessive even for an 'extended' server.

    Completeness3/5

    The tool surface covers several important domains (interception, emulation, CSS, accessibility, performance) but lacks core page control operations like navigation, JavaScript evaluation, or element interaction. This leaves noticeable gaps for common testing workflows, though it can still handle scenarios where a page is already loaded.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources