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.
      1,516,489 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
      243
      MIT

    • 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.
      1,516,489 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

    C2.9/5.0

    Scored across 64 tools

    Disambiguation3/5

    Several tools overlap significantly: browser_batch duplicates nearly every individual action, browser_block_urls and browser_block_resources both block resources, and browser_emulate_environment overlaps with browser_set_geolocation and browser_set_timezone. Descriptions help somewhat, but an agent could easily choose the wrong tool for a task.

    Naming Consistency4/5

    All tools use the browser_ prefix with snake_case, which is highly consistent. Minor deviations exist (e.g., singular/plural mismatch in browser_get_cookies vs browser_set_cookie, and some tools are just nouns like browser_history).

    Tool Count1/5

    64 tools is far too many for an MCP server; the rubric treats 50+ as an extreme mismatch. Many tools are redundant granular actions that could be consolidated, especially since browser_batch can perform most of them.

    Completeness4/5

    The surface covers navigation, tabs, interactions, network, storage, emulation, CDP, and extensions very thoroughly. A few gaps remain (e.g., no dedicated set_storage, wait_for_selector, or specific cookie deletion), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources