Skip to main content
Glama
Sign In
pyside6-mcp

pyside6-mcp

by com55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pyside6-mcp

No user-submitted related servers found.

    Related Servers

    • qtpy-mcp

      ColinKennedy
      A
      license
      B
      quality
      B
      maintenance
      Enables an AI agent to find, screenshot, GIF-record and drive Qt widgets inside running Qt applications and DCCs such as Houdini, Blender, Maya and Nuke, working across PySide6, PyQt6, PySide2 and PyQt5. It routes one agent connection to many applications at once, offering semantic widget search, widget-tree inspection, clicking/typing, and per-window or per-panel captures.
      30
      1
      Apache 2.0

    • qt-mcp

      0xCarbon
      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

    • uiautomation-mcp

      miloira
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      14 PyPI
      MIT

    • electron-viewer

      acertijosapps
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets an AI agent launch or attach to a running Electron app and control it directly over the Chrome DevTools Protocol: capture screenshots (optionally with the native window frame), click, drag, hover, scroll, type, press keys, resize and reload. It also exposes JavaScript execution in both the renderer and main process, an accessibility tree with click-ready coordinates, and console logs, so an agent can inspect and operate the app without adding any code to it.
      553 npm
      MIT

    • electron-mcp-bridge

      rudraptpsingh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to attach to an already-running Electron desktop app and inspect both the Node.js main process and Chromium renderer, invoking IPC channels, evaluating renderer scripts, capturing screenshots, and reading diagnostics. It also lets apps expose custom verification oracles so agents can confirm real business effects like database rows, file sidecars, and hash receipts instead of just UI changes.
      85 npm
      MIT

    • opencode-gui-bridge

      Yueqi-Wang-795
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources