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.
      75 npm
      15
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An accessibility-first Windows computer-use MCP server that lets AI agents find and click real UI Automation controls, falling back to a vision model of your choice only when a control isn't exposed. Agents get short text results instead of screenshots while driving the real mouse and keyboard, with a visible control panel and hard stops.
      Apache 2.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
      B
      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.
      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.
      151 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 37 tools

    Disambiguation4/5

    The browser_ prefix clearly separates Chrome-tab tools from native-app tools, and descriptions repeatedly cross-reference the correct counterpart. However, paired tools such as browser_click vs click, browser_type vs type_text, and browser_fill vs set_value still require careful reading to avoid misselection.

    Naming Consistency4/5

    Most tools follow a predictable snake_case verb_noun pattern, with the browser_ prefix consistently marking browser operations. Minor deviations such as screenshot, browser_snapshot, browser_page_errors, and clipboard_read/clipboard_write keep it from being perfectly uniform.

    Tool Count3/5

    The server has 37 tools across two large domains, browser automation and native desktop control. Each tool has a defensible role, but the surface is heavy and contains many near-paired operations that increase selection burden.

    Completeness4/5

    Coverage is strong: browser lifecycle, navigation, snapshots, reading, input, uploads, dialogs, credentials, and page errors are present, alongside native app state, screenshots, input, clipboard, and multi-step execution. Minor gaps exist for browser-specific hover, scrolling, and drag interactions, though many tasks can work around them.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled