Skip to main content
Glama
Rainmen-xia

Chrome Debug MCP Server

by Rainmen-xia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Chrome Debug MCP Server

No user-submitted related servers found.

    Related Servers

    • Chrome MCP Server

      lxe
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to control Chrome browsers through the Chrome DevTools Protocol, allowing for navigation, clicking, typing, and extracting page information.
      107 npm
      49
      MIT

    • SmartBrowserMCP

      Jenish3601
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server for web automation that enables browser control, element interaction, content extraction, and monitoring using Playwright.
      7
      6 npm
      ISC

    • Chromate MCP

      69gg
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for Chrome tab automation using the Chrome DevTools Protocol, enabling AI agents to select tabs, capture screenshots, and interact with web pages via CSS viewport coordinates.
      9
      MIT

    • unified-browser-mcp

      msawayda
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that combines Playwright browser automation with DevTools-style monitoring capabilities, enabling AI assistants to automate browser tasks and capture network/console logs.
      13
      5 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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: click, hover, type_text handle different user interactions; navigate_to, scroll_up/down manage navigation; launch_browser, close_browser, resize_browser control browser state; get_page_content retrieves content. The descriptions clearly differentiate actions like click vs hover or scroll_up vs scroll_down.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern throughout (e.g., get_page_content, navigate_to). The verb-noun structure is mostly predictable, though some tools use simple verbs like click or hover without objects, which is a minor deviation from the full verb_noun pattern seen in others like resize_browser.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a Chrome debugging server. Each tool earns its place by covering essential browser automation tasks: launching/closing, navigation, interaction (click, hover, type), scrolling, resizing, and content retrieval. This provides a balanced set without being overwhelming or too sparse.

    Completeness4/5

    The toolset covers core browser automation workflows well, including setup (launch_browser), navigation (navigate_to, scroll), interaction (click, hover, type_text), and teardown (close_browser). Minor gaps exist, such as no explicit tool for handling pop-ups, taking screenshots, or executing JavaScript, but agents can work around these with the provided tools for most debugging tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources