Skip to main content
Glama

Related Servers

Alternatives to veilbrowser

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      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.
      11
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control the user's already-open, logged-in browser pages in real time over a local WebSocket channel, without Playwright, Puppeteer, Selenium, or any browser driver. Exposes tools for navigation, semantic page snapshots, clicking, form filling, JavaScript evaluation, screenshots, network monitoring, cookie handling, and tab management via the CDP.
      20
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to browse and interact with web pages using a stealth Chromium browser, with an accessibility-tree interface for low token usage.
      12
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive a Chromium browser over MCP, reading pages as a numbered list of controls and performing actions like clicking, filling forms, and asserting page state without screenshots or API keys.
      10
      814 PyPI
      18
      MIT

    TDQS

    A3.7/5.0

    Scored across 33 tools

    Disambiguation5/5

    Each tool targets a specific browser automation action with minimal overlap. For example, 'veil_fill' is for clicking a field and typing, while 'veil_type' is for typing into the focused element, and descriptions clearly distinguish them.

    Naming Consistency5/5

    All tools follow a consistent 'veil_' prefix with a verb or verb_noun pattern, such as 'veil_goto', 'veil_set_viewport', 'veil_wait_for_selector', making the naming predictable and intuitive.

    Tool Count4/5

    With 33 tools, the server covers a broad range of browser automation needs (navigation, interaction, extraction, resource control, etc.), which is appropriate for its comprehensive scope, though slightly on the higher side.

    Completeness4/5

    The tool set covers most essential browser automation operations, including navigation, interaction, data extraction, resource blocking, fingerprinting, and screenshots. Missing features like dialog handling are minor and do not hinder typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues