Skip to main content
Glama

Related Servers

Alternatives to Computer Use

No user-submitted related servers found.

    Related Servers

    • 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
      D
      maintenance
      An open-source MCP server for macOS and Windows that provides native desktop control via Accessibility APIs, OCR, and Chrome CDP. It enables AI agents to interact with applications, manage browser sessions, and automate workflows with high-speed native UI actions.
      28 npm
      15
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      macOS MCP server that enables AI agents to directly control the host OS, including mouse, keyboard, windows, files, and accessibility automation for computer-use workflows.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents real OS-level control of macOS, enabling them to click real buttons, type real keys, and observe rendered screens just like a human would.
      44 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local, dependency-free MCP server that gives AI agents controlled access to the active Windows desktop, enabling automated interaction with applications through screenshots, clicks, typing, and window management.
      43 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      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
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 32 tools

    Disambiguation4/5

    The browser-prefixed tools are cleanly separated from native-app tools, and descriptions explicitly explain when to use browser_click versus click, browser_type versus type_text, and browser_press_key versus press_key. However, there is still conceptual overlap around text entry, clicking, and reading state across browser and native contexts that an agent must track carefully, and tools like set_value, type_text, browser_type, and clipboard_write all touch text input.

    Naming Consistency3/5

    The browser tools follow a consistent browser_verb pattern, but the native-app tools mix bare verbs (click, drag, hover), noun-like names (screenshot, zoom), and get/set/list forms (get_app_state, set_value, list_apps, list_displays). The split convention is meaningful, but within the native-app set naming is only somewhat predictable.

    Tool Count3/5

    With 32 tools, the surface is heavy for a single server, though the domain realistically spans browser tab management, page reading/interaction, native app accessibility, screenshots, and clipboard access. Some redundancy exists between browser-specific and native-app analogues, suggesting consolidation could reduce the count, but most tools do correspond to distinct operations.

    Completeness4/5

    Coverage is broad: browser tabs, navigation, snapshots, clicks, typing, credentials, native app state, screenshots, zoom, drag, clipboard, and cleanup are all represented. Minor gaps exist around richer browser interaction such as file uploads or full window management, but the practical automation surface is largely complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week