Skip to main content
Glama
kqlio67

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fast Browser MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      2,262,793 npm
      Apache 2.0

    • Browser-Debugger

      Selvadinesh-giga
      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
      -

    • Blinkwire

      81117105108108
      A
      license
      B
      quality
      B
      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

    • agent-browser-mcp

      335234131
      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
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.1/5.0

    Scored across 69 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes (navigate, click, screenshot, tabs), but several clusters overlap: browser_block_urls vs browser_block_resources, browser_set_geolocation/timezone vs browser_emulate_environment, browser_clear_storage vs browser_get_storage, and browser_set_cookie vs browser_get_cookies. The massive browser_batch tool also duplicates ~35 individual actions, creating real selection ambiguity.

    Naming Consistency5/5

    Every tool uses a consistent browser_ snake_case prefix with a clear verb_noun structure (browser_new_tab, browser_get_cookies, browser_set_timezone). The convention is applied uniformly across all 69 tools with no style drift.

    Tool Count1/5

    69 tools is an extreme mismatch for a single browser-automation server, far beyond the typical 3-15 range. Many capabilities are redundant (batch duplicates individual tools) and the sheer surface makes discovery and correct selection impractical.

    Completeness5/5

    Coverage is exhaustive across navigation, interaction, network capture, storage, emulation, extensions, stealth, performance, and raw CDP escape hatch. There are essentially no gaps in the browser-automation lifecycle; if anything it over-covers the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources