Skip to main content
Glama

Related Servers

Alternatives to Fast Browser MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      2,051,149 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate and debug real Chromium browsers with capabilities like screenshots, video recording, performance analysis, visual regression testing, and OCR text extraction.
      13
      -
    • A
      license
      B
      quality
      C
      maintenance
      Provides fast, token-efficient browser automation for LLMs by attaching directly to a running Chrome instance via CDP, offering a full set of browser tools including navigation, interaction, and snapshot diffs, with batched actions to reduce round-trips.
      56
      GPL 3.0
    • A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      245
      MIT
    • 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.
      2,051,149 npm
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 64 tools

    Disambiguation3/5

    Most tools have clear distinct purposes, but several overlapping pairs exist: browser_block_urls vs browser_block_resources, browser_emulate_environment vs browser_set_geolocation/browser_set_timezone, and browser_mouse vs browser_click. The browser_batch and browser_cdp_send tools also subsume many others, creating boundary ambiguity.

    Naming Consistency3/5

    All tools share the browser_ prefix and snake_case convention, but the pattern is inconsistent: some use verb_noun (browser_navigate, browser_clear_storage), while others are bare nouns (browser_console_logs, browser_history, browser_mouse) or have irregular verbs (browser_eval, browser_batch). Still readable and predictable at a high level.

    Tool Count1/5

    64 tools is an extreme count for a single server, especially given that browser_batch consolidates dozens of actions and browser_cdp_send provides raw universal access. Many tools could be folded into the batch or CDP surfaces, making the set feel bloated rather than well-scoped.

    Completeness5/5

    The tool surface is remarkably comprehensive for browser automation: navigation, tabs, history, storage (local, session, IndexedDB), cookies, network inspection, console logs, emulation, performance, extensions, permissions, file upload, PDF, screenshots, and preload scripts are all covered. There are no obvious dead ends for typical browser workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive