Skip to main content
Glama
ingjohnfigueroablanco

Browser-MCP Navigator

Related Servers

Alternatives to Browser-MCP Navigator

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      A lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.
      26
      51 npm
      19
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight MCP server for browser automation that gives AI agents navigate, screenshot, and extract tools via a single small binary, without needing Node.js or Playwright. It provides CDP-based browser control with efficient startup and resource usage.
      24
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      An MCP server that gives AI clients direct control over driverless Chromium browsers through the Chrome DevTools Protocol, enabling agents to navigate pages, click, type, inspect the DOM, capture console and network traces, and manage tabs, cookies, and storage. It supports persistent profiles, proxy and locale alignment, and a live VNC viewer so users can build, test, and debug web automations interactively.
      70
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      single-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.
      14
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -

    TDQS

    B3.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., click vs js_click vs cdp_call), but the difference between click and js_click might confuse an agent without careful reading. Overall, each tool targets a unique action.

    Naming Consistency3/5

    All names use snake_case, but the pattern mixes simple verbs (click, hover, scroll) with verb_noun phrases (get_text, read_console, press_key) and compound noun_verb (js_eval, cdp_call). This inconsistency, while still readable, could be improved.

    Tool Count4/5

    21 tools is slightly above the typical 3-15 range, but each tool serves a specific need in browser automation (navigation, interaction, JavaScript execution, bulk operations, etc.). The count feels justified for the domain.

    Completeness4/5

    Covers essential browser automation operations: navigation, clicking, typing, scrolling, waiting, reading page state, console/network monitoring, and JavaScript execution. Missing a dedicated file upload tool, but can be done via cdp_call. Minor gaps overall.

    Maintenance

    ActivityStale
    ResponsivenessNo issues