Skip to main content
Glama
adkdev200

Universal Computer Control MCP

by adkdev200

Related Servers

Alternatives to Universal Computer Control MCP

No user-submitted related servers found.

    Related Servers

    • F
      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
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Windows by clicking, typing, and navigating with a visible cursor overlay, using a layered approach (native UIA, browser CDP, pixel fallback) for reliable interaction.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight server that enables AI agents to interact with the Windows operating system, allowing for file navigation, application control, UI interaction, and QA testing through various tools.
      7,293
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables an AI agent to control a Windows PC through human-like interactions such as screen capture, OCR, mouse, keyboard, and navigation, without using shortcut APIs.
      -
    • A
      license
      Not graded
      quality
      B
      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.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents and MCP clients direct control over native desktop apps, Chrome/Electron browsers, and Android devices with screenshots, OCR, accessibility-based element lookup, input simulation, window management, CDP, and ADB in one local server.
      133
      MIT

    TDQS

    B3.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a single, distinct action or resource, and the shared target resolution rules do not create real confusion. The main overlap is that observe subsumes screenshot and get_ui_tree, while find_text and find_visual both locate on-screen targets, but their text-vs-visual distinction keeps them usable.

    Naming Consistency4/5

    The majority of tool names follow a clear action_object snake_case pattern, such as focus_window, get_clipboard, and list_windows. A few outliers like observe, screenshot, backend_status, and emergency_stop break the verb_noun pattern but remain readable and stylistically consistent.

    Tool Count2/5

    At 29 tools, the namespace is too large for a single agent-facing surface; the selection cost is significant even though the tools cluster into clear functional groups. Some observation tools such as screenshot, observe, and get_ui_tree could be consolidated, which would reduce count without losing capability.

    Completeness5/5

    The set covers the full GUI automation loop: observing state, searching for targets, input, window lifecycle, clipboard, launching applications, shell commands, and safety controls. There are no obvious dead ends, and wait_for plus backend_status close the verification and error-handling gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues