Skip to main content
Glama
axe-work

Quest Browser MCP Server

by axe-work

Related Servers

Alternatives to Quest Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control the user's already-open, logged-in browser pages in real time over a local WebSocket channel, without Playwright, Puppeteer, Selenium, or any browser driver. Exposes tools for navigation, semantic page snapshots, clicking, form filling, JavaScript evaluation, screenshots, network monitoring, cookie handling, and tab management via the CDP.
      20
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.
      63
      10 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive browser automation and control through Playwright, including launching browsers, managing tabs, web navigation, element interaction, and screenshot capture. Supports detecting and controlling external browsers with remote debugging capabilities.
      -
    • 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,204,746 npm
      3
      Apache 2.0

    TDQS

    C2.7/5.0

    Scored across 57 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes, such as browser_resize vs browser_set_viewport_size, browser_snapshot vs browser_get_accessibility_tree, and browser_get_network_logs vs browser_network_requests. The wait_for_* family also has several similar options (load, navigation, url, response) that can be confused.

    Naming Consistency4/5

    Tool names consistently follow the pattern of prefix (adb_ or browser_) plus verb_noun, e.g., browser_navigate, browser_get_title, browser_set_geolocation. Minor deviations like browser_resize (verb only) and browser_snapshot (noun) are exceptions but the overall pattern is readable and predictable.

    Tool Count1/5

    With 57 tools, the set is excessively large for a browser automation server. Many are near-duplicates (resize/set_viewport_size, snapshot/get_accessibility_tree, network_logs/network_requests), inflating the count without adding genuine functionality. This is well beyond the typical heavy range of 25+.

    Completeness4/5

    The tool set covers a broad range of browser automation needs, including navigation, interaction, waiting, network monitoring, accessibility, file upload, and ADB port forwarding. However, it lacks cookie management and cannot create new browser pages (only connects to existing ones), which are notable gaps for a fully complete browser automation surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues