Skip to main content
Glama

Related Servers

Alternatives to navigera

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that lets AI agents drive the locally installed Chrome or Edge, opening pages, taking compact accessibility-tree snapshots with @e references, and clicking, typing, scrolling, or capturing screenshots. It also exposes multi-account and cross-channel tab switching, tab sync rules, and ad-block/perf statistics.
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Native webview browser automation for AI agents. Rust-powered, with JSON-lines control and a built-in MCP server. Runs on macOS, Linux, and Windows.
      43
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      10 npm
      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
      A
      quality
      A
      maintenance
      MCP server for AgentGo, a real Chromium browser for AI agents: compact page outlines with stable refs, diff-only replies after each action, real mouse and keyboard input, the agent's own signed-in accounts, and human approval for payments. MIT.
      11
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools map to a single, distinct browser primitive, and descriptions actively steer between near-neighbors (browser_fill vs browser_type, browser_snapshot vs browser_screenshot, browser_click vs browser_mouse, browser_scroll vs browser_mouse wheel). The remaining overlaps — several ways to read a page (snapshot, screenshot, evaluate, console, network) and browser_run duplicating single-step ops — are explained but still require the agent to choose.

    Naming Consistency5/5

    Every tool uses the same browser_ prefix with a snake_case verb or noun phrase (browser_navigate, browser_click, browser_press_key, browser_wait_for). No camelCase or mixed-convention outliers; names are predictable and readable.

    Tool Count4/5

    23 tools is at the upper end of comfortable, but the surface is a genuinely broad browser-automation domain (input, inspection, debugging, tabs, dialogs, files, handoff) and no tool looks like filler. It is slightly heavy rather than bloated.

    Completeness4/5

    Coverage is strong across navigation, input, waits, tabs, history, dialogs, uploads, console/network inspection and a batch runner, with an escape hatch via browser_evaluate. Gaps are minor but real: no cookie/localStorage management, no explicit download handling, and no frame/iframe switching (workable only through evaluate).

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive