Skip to main content
Glama

Related Servers

Alternatives to Finitact

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      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
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to see, locate UI elements, and operate any Windows desktop app through natural language, using accessibility-tree matching with optional vision-model fallback, plus an autonomous visual loop with introspection and meta-learning.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect and drive native Windows desktop applications (WinForms, WPF, WinUI 3, and WebView2 hybrids) through Microsoft UI Automation by capturing interactive control snapshots, then clicking, filling, and asserting on elements via ephemeral refs or semantic screen-map targets. Mutating actions are dry-run by default and gated behind explicit arming, allow-lists, and a kill switch for lawful, assisted QA testing.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to operate Windows applications through recursive grid-based screenshot navigation and proportional coordinates, with UIAutomation, mouse/keyboard control, sequential batch actions, and input locking.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables safe Windows desktop automation and computer use through natural language, including window observation, UI Automation, and execution of verified actions like clicking, typing, and scrolling.
      2
      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 issues