Skip to main content
Glama
aethyn-io

aethyn-browser-mcp

Official
by aethyn-io

Related Servers

Alternatives to aethyn-browser-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server giving AI agents controlled residential-proxy web access with optional browser rendering and structured extraction from 60+ sites.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that exposes browser-drive tools over a local endpoint, letting AI agents launch and control isolated browser profiles with their own cookies, fingerprints, and proxies, then navigate, click, type, extract, screenshot, evaluate JS, and manage tabs and cookies. Session state persists across launches so authenticated workflows carry over between AI sessions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to control a real browser with your existing sessions and extensions, avoiding bot detection and authentication hurdles.
      106
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.
      15
      8 npm
      3
      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

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: launching, navigating, interacting via click/type, extracting content, managing identity, checking exit IP, listing countries, and cleanup. No ambiguity between any pair.

    Naming Consistency5/5

    All tools follow a consistent aethyn_verb_noun snake_case pattern (e.g., aethyn_launch_browser, aethyn_check_exit_ip). No mixing of styles or unpredictable naming.

    Tool Count5/5

    10 tools cover the full lifecycle of browser automation with proxy support: launch, navigate, interact, extract, identity rotation, geo discovery, and cleanup. The count is well-scoped for the domain.

    Completeness4/5

    The tool set covers all core browser automation steps: launch, navigate, interact (click, type), extract (content and snapshot), identity management, and exit verification. Minor gaps like screenshots or explicit waits are intentionally omitted, but the core workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues