Skip to main content
Glama

Related Servers

Alternatives to web-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that gives AI coding assistants direct access to the browser — navigate, click, fill forms, run JavaScript, take screenshots, and read page content.
      11
      19 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to visually inspect and interact with rendered web pages via a persistent headless Chromium browser, supporting navigation, screenshots, clicks, viewport resizing, and console log retrieval.
      8
      1
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI coding tools to control a browser for automated actions, UI extraction, network interception, and screenshots.
      23
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for browser automation and console log capture via a Chrome extension, enabling AI-driven DOM interaction, navigation, and screenshot capabilities.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      3 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.
      99
      7 npm
      3
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action or read: list_pages enumerates contexts, get_guide is meta-documentation, eval_js is the generic execution escape hatch, and click/type/hover/focus/scroll_to cover specific interactions. Although eval_js could technically perform many of the specialized operations, the specialized tools have clearly separated purposes and the descriptions reinforce the boundaries.

    Naming Consistency4/5

    Names are uniformly lowercase and follow a readable functional pattern: get_* for state/read operations, bare verbs for direct actions, and wait_for/scroll_to for prepositional actions. Minor deviations from a strict verb_noun convention (click, type, wait_for) are not confusing but prevent a perfect score.

    Tool Count5/5

    Thirteen tools is well-scoped for a browser-automation bridge: discovery, execution, console access, DOM reading, waiting, interaction, and two complementary visual verification tools. Each tool has a distinct role and none feels redundant or missing in the immediate set.

    Completeness4/5

    The surface covers the core browser workflow well: list pages, execute JS, read logs/text, wait for conditions, interact, focus, scroll, and verify via DOM or screenshot. There is no dedicated navigation, keyboard, or page-lifecycle tool, but eval_js and the existing interaction tools provide reasonable workarounds for those gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues