Skip to main content
Glama
qt-commander
by tiefeiyu

Related Servers

Alternatives to qt-commander

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for inspecting, debugging, and interacting with PySide6 desktop applications. It enables AI agents to capture UI snapshots, read widget properties, and perform actions like clicking buttons or typing text.
      22
      3
      Apache 2.0
    • 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
      Enables MCP-enabled agents to test a running C++ Qt GUI application headlessly by discovering and interacting with UI controls, detecting popup errors, inspecting Qt logs, capturing screenshots, and running readable UI-test scripts.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for capturing screenshots of Qt/desktop windows and performing filesystem operations, enabling AI clients to inspect and modify project files.
      15
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.
      23
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      142
      MIT

    TDQS

    A4.1/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, but the three mouse click variants (qt_mouse_click, qt_mouse_click_region, qt_mouse_click_at) are closely related and could be confused. Their descriptions clearly explain the differences in delivery mechanism and use cases, so ambiguity is mostly resolved.

    Naming Consistency5/5

    All tool names follow a consistent qt_verb_noun pattern with lowercase underscores (e.g., list_processes, get_property, mouse_click). Minor abbreviations like 'dbl' in qt_mouse_dbl_click are negligible and do not disrupt the overall predictability.

    Tool Count4/5

    With 25 tools, the server is on the heavier side, but each tool maps to a distinct step in Qt UI automation—from environment detection and build to attach, inspection, and input simulation. The granularity is justified by the complexity of the domain.

    Completeness5/5

    The tool set covers the entire lifecycle: detect environment, build, attach, snapshot/find elements, read/write properties, call methods, simulate mouse and keyboard input, and detach. No obvious gaps prevent agents from accomplishing UI automation tasks.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues