Skip to main content
Glama

Related Servers

Alternatives to Finitact

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to perceive and control a Windows desktop, a connected local Chromium browser, or a cloud Playwright browser through human-like mouse moves, clicks, drags, scrolling, and screenshots, forming an observe-locate-act computer-use loop. Includes safety guards such as random pauses, emergency stop, and approval prompts for destructive actions.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to drive a selected Windows application toward a natural-language goal by reading the UI with local OCR/UIA and deciding next actions.
      6
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to operate websites and Windows desktop applications by reading and acting on webpage elements, exposed UI controls, and screenshots with mouse and keyboard input. Combines browser, desktop, and computer-control channels in a single task, with an optional target selector for batched actions.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI model see an indexed UI Automation accessibility tree of Windows desktop apps and act on it with precise clicks, typing, key chords, scrolling, dragging, and element value changes, using window captures that work even for occluded windows. Screenshot-based coordinates are rescaled and validated against the target window so input fails loudly instead of hitting the wrong app.
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and operation: list Windows targets, run browser goals, run Windows UI goals, observe browser pages, observe Windows labels, cancel a run, and read a run journal. The browser/window split is consistently reflected in both run and observe tool names. No two tools appear interchangeable.

    Naming Consistency5/5

    All tool names use snake_case with a verb-first pattern: list_windows, run_browser, run_windows, observe_browser, observe_window, cancel_run, get_run_journal. The convention is predictable and readable throughout.

    Tool Count5/5

    Seven tools is well-scoped for a UI and browser automation control server. Each tool covers a necessary capability without obvious redundancy or missing core surface.

    Completeness4/5

    The set covers the core automation lifecycle: target discovery, running browser and Windows goals, observing results, cancelling runs, and reading journals. Minor gaps remain, such as no explicit way to enumerate existing browser tabs or manage/close kept tabs beyond the run_browser keep_tab flow, and no list-active-runs tool. These are workable limitations rather than severe omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues