Skip to main content
Glama

Related Servers

Alternatives to nexus-browser

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to drive the user's already-running Google Chrome through a WebSocket bridge, listing and switching tabs, navigating, clicking, typing, scrolling, extracting DOM, taking screenshots, and evaluating JavaScript. It works without restarting Chrome and preserves all existing logins, cookies, and 2FA sessions.
      25
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents control the real, already-logged-in Chrome browser: reading pages, clicking, typing, navigating tabs, taking screenshots, and inspecting cookies, network traffic, console output, and storage. It connects as a local extension over Native Messaging, so no remote-debugging port or headless profile is needed.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control Chrome, Edge, Brave and other Chromium browsers through an extension and native messaging host, exposing a Claude-in-Chrome-compatible tool set for real clicks, typing, screenshots, accessibility-tree reading, page text, form filling, JavaScript execution, console and network inspection, file uploads and GIF recording. Agent sessions run in isolated tab groups with per-site permission prompts, activity logging and a global stop control.
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to create, read, and operate granted background tabs in Chrome via a local stdio MCP server, preserving the human's front tab. Supports tab groups, navigation, clicking/typing, screenshots, and human-priority permissions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to locally drive the user's own logged-in Chrome browser, including clicking, typing, reading pages, taking screenshots, running JavaScript, recording GIFs, and coordinating parallel agents across Chrome profiles and tab groups.
      MIT

    TDQS

    A3.5/5.0

    Scored across 49 tools

    Disambiguation3/5

    Most tools target distinct actions, but several overlap in reading/inspecting the page: browser_content, browser_export, browser_axtree, browser_interactive_map, browser_find, browser_vision_inspect and browser_screenshot all serve discovery/extraction, and browser_eval vs browser_cdp_send(Runtime.evaluate) both run code. Descriptions are rich enough to guide selection, but an agent can easily pick the wrong extraction or inspection tool.

    Naming Consistency4/5

    All names share the browser_ prefix and snake_case, forming a predictable family. Minor deviations exist: some names are verbs (browser_click, browser_navigate) while others are nouns (browser_content, browser_axtree, browser_logs, browser_pdf), which is readable but not perfectly uniform.

    Tool Count2/5

    49 tools is far above the typical 3-15 well-scoped range and makes the surface heavy. While browser automation is broad, several tools (cdp_send, eval, webmcp, gsuite export) feel like specialized add-ons rather than core workflow tools.

    Completeness4/5

    Coverage is extensive: navigation, tabs, interaction, waits, network, downloads, exports, screenshots, and handoff/2FA checks are all present. Minor gaps exist around direct cookie/storage mutation and browser-level (non-tab) control, but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues