pyside6-mcp
Related Servers
Alternatives to pyside6-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn 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.222Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and automate Windows desktop UI elements by exploring UI trees, checking properties, performing actions like clicking and typing, and generating Python automation scripts.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Windows GUI by listing and focusing windows, capturing element snapshots via UIA/OCR/CDP, performing clicks/inputs/scrolls, verifying changes, waiting for screen updates, taking screenshots, and obtaining visual descriptions.2-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to observe and control the user's live desktop by listing apps, reading accessibility trees, and performing clicks, typing, scrolling, dragging, and other input actions with per-action approvals and local audit archives.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, automate, and test desktop GUI applications on Wayland through window/desktop streaming, semantic AT-SPI accessibility tree inspection, and boundary-clamped mouse, keyboard, drag, and scroll input injection. It also manages application process lifecycle, captures window frames, and registers Python GUI scripts as native Linux desktop launchers.MIT
- AlicenseAqualityAmaintenanceMCP 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.252MIT
TDQS
Scored across 22 tools
Most tools target distinct resources/actions: screenshot/tree/info/find for inspection, click/type/press/scroll for input, launch/stop/status for lifecycle. A couple of pairs could be confused: wait_until_ready vs wait_for_idle and get_app_state vs get_app_status, though their descriptions separate them.
The set predominantly uses snake_case verb phrases such as get_widget_tree, list_actions, launch_app, and trigger_action. Minor deviations like the noun command 'screenshot' and a few bare verbs (click, scroll) keep it from being perfectly uniform, but the overall pattern is predictable.
22 tools is on the heavy side for an MCP surface, and some functionality (wait_until_ready/wait_for_idle, get_app_state/get_app_status, get_logs/get_app_output) could potentially be consolidated. Still, the count is defensible given the breadth of UI automation and debugging features.
The set covers the full lifecycle of launching, inspecting, interacting with, waiting on, and stopping a PySide6 app, plus logs and QAction access. There are minor gaps such as no direct property-mutation or drag/drop tool, but eval_python and existing input tools provide workarounds.