Skip to main content
Glama

Related Servers

Alternatives to BrowserMCP Extended

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI assistants to drive the user's real, already-logged-in Chrome browser locally, so they can read and summarize pages, click, type, fill and submit forms, navigate tabs, and capture screenshots with full access to existing sessions. It also exposes cookies, storage, console, network capture, and emulation capabilities without opening a remote-debugging port or sending data off the machine.
      1 npm
      ISC
    • 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to drive the Chrome or Edge tabs you already have open and signed in, by pairing with a local browser extension instead of launching a remote debugging port or a separate automation browser. Exposes 20 tools for accessibility-tree snapshots, clicking and filling, navigation, uploads, screenshots, JavaScript evaluation, and console and network log reading.
      24
      210 npm
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Turns Chrome into a local MCP server, giving AI agents 51 browser tools to inspect DOM, automate clicks, run JavaScript, audit security and accessibility, mock APIs, extract data, record demos, and more from any MCP client.
      92
      77 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 39 tools

    Disambiguation3/5

    Most tools target a distinct resource+action, but browser_drag and browser_drag_drop appear to be near-duplicates with only a CSS-selector phrasing difference, forcing an arbitrary choice. Content-retrieval tools (browser_get_text, browser_get_html, browser_snapshot, browser_screenshot_element) also overlap somewhat, though descriptions provide workable guidance.

    Naming Consistency3/5

    The browser_ prefix is applied almost everywhere, but conventions mix: verb-first names (browser_click, browser_type, browser_get_text) sit alongside resource-then-verb names (browser_network_list, browser_network_detail, browser_screenshot_element). execute_script breaks the prefix entirely, and browser_drag vs browser_drag_drop is an inconsistent naming of essentially the same operation.

    Tool Count2/5

    At 39 tools the surface is heavy for a browser-automation server, and several clusters could be consolidated: three screenshot variants, six network-capture tools, and two drag implementations. Individually justifiable, but as a set it exceeds a comfortably scannable scope.

    Completeness4/5

    Coverage is broad: navigation, tabs, interaction, cookies, storage, console logs, dialogs, iframes, uploads, screenshots, and full network capture with HAR export. Minor gaps remain (no viewport/device emulation, no read-clipboard, no selector-based wait, no storage writes), but agents can work around them.