Skip to main content
Glama

Related Servers

Alternatives to browser-ai

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control Chrome reliably over MCP, including multi-tab browsing, forms, clicks, keyboard, scrolling, drag, uploads, downloads, dialogs, JavaScript evaluation, and console/network inspection, in headed or headless mode or attached to an existing Chrome instance.
      22
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.
      688 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control the Google Chrome browser through a Node.js WebSocket bridge and a dedicated browser extension. It provides tools for capturing screenshots, executing JavaScript, managing tabs, and extracting page content via the MCP protocol.
      2
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
      1
      -

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool maps to a distinct browser action: tab lifecycle (list/new/close/switch), history (back/forward), navigation, inspection (read/html/eval/screenshot/pdf), and interaction (click/type/wait). The only mild overlap is web_eval versus web_read/web_html, but eval's arbitrary-JS purpose is clearly differentiated. An agent can reliably pick the right tool for a given intent.

    Naming Consistency4/5

    All tools share a consistent 'web_' snake_case prefix, which makes the set instantly recognizable. Minor deviation: some names are verbs (web_click, web_navigate) while others are nouns (web_tabs, web_screenshot, web_html), but the convention remains readable and predictable.

    Tool Count5/5

    Fifteen tools is well within the sweet spot and each one earns its place by covering a real browser primitive. There is no redundancy or filler in the surface.

    Completeness4/5

    Core lifecycle is fully covered: tab management, navigation, history, content extraction, interaction, waiting, and export (screenshot/PDF). Notable gaps remain for common automation needs — hover, select-option for dropdowns, keyboard key presses, scrolling, and iframe/frame targeting — which agents may have to work around via web_eval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues