Skip to main content
Glama

Related Servers

Alternatives to OpenEyes

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Cross-platform desktop automation MCP server that lets AI agents capture screenshots, run OCR with UI-element classification, control mouse/keyboard, and launch programs on Linux, macOS, and Windows.
      20
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives any AI assistant eyes and hands on your desktop — screenshots, clicking, typing, OCR, window management, accessibility-tree queries, workflow recording.
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      GUI automation MCP server that enables AI agents to see and control the Windows desktop using a local Vision LLM (Ollama), supporting screenshot analysis, mouse/keyboard actions, and autonomous task execution.
      5
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets an LLM see and drive any running Windows app: attach a window, screenshot it, read its UI Automation tree, and send clicks, typed text, and key presses with pixel coordinates.
      -

    TDQS

    B3/5.0

    Scored across 23 tools

    Disambiguation3/5

    The descriptions do real work differentiating close pairs (click_by_id vs click vs grid vs browser_click; anchor_probe vs anchor_wait; browser_scan vs detect_elements vs resolve_elements), but there are still four element-enumeration tools and four click paths whose boundaries an agent must infer from prose rather than names. Overlap between scene_describe, capture_window, and browser_shot for 'look at the screen' adds further selection risk.

    Naming Consistency3/5

    Everything is snake_case, and prefix families (browser_*, anchor_*) are used consistently, which helps. But the grammar is mixed: verb_noun (click_by_id, capture_window, list_windows, detect_elements), noun_verb (app_ensure, scene_describe, anchor_probe, record_replay), and bare nouns (grid, hotkey, native_surfaces), so the pattern isn't predictable across the set.

    Tool Count3/5

    23 tools is on the heavy side, and the surface spans three tiers (browser CDP, Windows UIA, vision/anchors) plus verification and replay. Each tool does map to a distinct capability tier, but the count is high enough that an agent must triage before acting.

    Completeness3/5

    Core lifecycle is well covered: launch/ensure app, enumerate, click, type, hotkey, capture, verify, and replay. Notable gaps remain — there is no scroll, drag, or navigation/URL-open tool, and no way to close or kill an app or window, which are common dead ends in an automation loop.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues