Skip to main content
Glama
null-runner

Chrome MCP Docker

by null-runner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Chrome MCP Docker

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.
      3,138,727 npm
      Apache 2.0

    • Chrome DevTools MCP

      ctrlShiftBryan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through DevTools for automated testing, performance analysis, debugging, and web scraping. Provides reliable browser automation using Puppeteer with comprehensive DevTools access.
      3,138,727 npm
      3
      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,138,727 npm
      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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: click, type, scroll, navigate, screenshot, wait_for_selector are standard browser actions; get_computed_styles, get_console_logs, get_network_errors are debugging tools; mobile_mode is a viewport toggle. No overlap or ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_computed_styles, get_console_logs, wait_for_selector) or are single verbs (click, scroll). 'mobile_mode' is a noun phrase, but still clear. Inconsistent usage of underscores (some have, others don't), but pattern is mostly predictable.

    Tool Count5/5

    10 tools is well-scoped for a browser automation server. Covers essential navigation, interaction, and debugging without redundancy. No unnecessary tools, and the count is within the ideal 3-15 range.

    Completeness3/5

    Core actions (navigate, click, type, scroll) and debugging (console logs, network errors, computed styles) are covered, but missing common operations like executing JavaScript, getting page source, handling alerts, managing cookies, or interacting with more complex form elements (select, checkbox). Agent may need workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources