Skip to main content
Glama

Related Servers

Alternatives to qt-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for automating and introspecting native Qt applications (QWidget and QML) without source changes. Enables AI agents to control running Qt apps through UI snapshots, element lookup, and real input simulation.
      25
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for headless Qt/PySide6 GUI testing that enables AI assistants to launch desktop applications via Xvfb and perform visual verification. It supports widget discovery, screenshot capture, and simulated user interactions like clicks, typing, and keyboard shortcuts.
      8
      MIT
    • A
      license
      A
      quality
      C
      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
      Not graded
      quality
      B
      maintenance
      An MCP server for inspecting and controlling running XAML applications across Avalonia, WPF, WinUI 3, and .NET MAUI, enabling AI clients to walk trees, modify properties, take screenshots, and send input.
      26
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists: qt_screenshot and qt_vtk_screenshot both capture images, and qt_snapshot and qt_object_tree both provide widget tree information, though they differ in scope (visible vs. full tree). The descriptions help clarify these distinctions, but an agent might occasionally confuse them.

    Naming Consistency5/5

    All tools follow a consistent 'qt_' prefix with snake_case naming, using clear verb_noun patterns (e.g., qt_click, qt_get_text, qt_list_windows). This predictability makes it easy for agents to understand and navigate the toolset.

    Tool Count3/5

    With 22 tools, the count feels heavy for a UI testing/automation server, potentially overwhelming for agents. While the tools cover various aspects (interaction, inspection, debugging), it might benefit from consolidation or better categorization to reduce cognitive load.

    Completeness5/5

    The toolset comprehensively covers the domain of Qt application testing and debugging, including widget interaction (click, type), inspection (snapshot, details), debugging (signals, threads), and specialized features (VTK, screenshots). No obvious gaps are present; agents can perform full workflows from discovery to validation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues