Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PySide6 MCP

PYPI · PYSIDE6-MCP · SCANNED SEP 20

Playwright-style MCP to inspect, control, and debug PySide6 desktop GUIs.

Available components

+4 this week 60 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2507 tokens (~113/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 46% of tool parameters carry a description.Partial
  • Structured output schemas are declared (95% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "eval_python" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the PySide6 MCP server?

PySide6 MCP runs locally as a PyPI package, launched with uvx pyside6-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · pyside6-mcp

# add to Claude Code
claude mcp add com55-pyside6-mcp -- uvx pyside6-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com55-pyside6-mcp": {
      "command": "uvx",
      "args": [
        "pyside6-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com55-pyside6-mcp": {
      "command": "uvx",
      "args": [
        "pyside6-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com55-pyside6-mcp -- uvx pyside6-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com55-pyside6-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "pyside6-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com55-pyside6-mcp --command uvx --arg pyside6-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com55-pyside6-mcp:
    command: "uvx"
    args: ["pyside6-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com55-pyside6-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "pyside6-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com55-pyside6-mcp -t stdio -c uvx -a pyside6-mcp
// mcp.json
{
  "mcpServers": {
    "com55-pyside6-mcp": {
      "command": "uvx",
      "args": [
        "pyside6-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +3
    • Stability: unverified → 0.27 functional
  • 10 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 9 Sept 26 −1
    • Malware scan: fail → unverified security
    • Security disclosure: fail → unverified functional
  • 8 Sept 26 +1
    • Malware scan: unverified → fail security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/pyside6-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~2,139 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
click ~137

Click a widget or screen coordinate. - widget_id only: clicks the center of that widget - widget_id + x/y: clicks at (x, y) relative to the widget's top-left - x/y only: clicks at (x, y) relative to the main window button: 'left' (default), 'right', or 'middle'

NameTypeReqDescription
buttonstring
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
widget_id
x
y
NameTypeReqDescription
resultstringyes

No examples provided.

double_click ~71

Double-click a widget. Sends two rapid left-clicks.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
widget_idstringyes
x
y
NameTypeReqDescription
resultstringyes

No examples provided.

eval_python ~132

Evaluate a Python expression or execute a statement inside the app process. Context provides: - app: QApplication instance - widgets: dict mapping widget_id → QWidget Examples: eval_python("app.activeWindow().windowTitle()") eval_python("widgets['3'].isEnabled()") eval_python("list(app.allWidgets())") WARNING: runs arbitrary code in the app — use only for debugging.

NameTypeReqDescription
codestringyes
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

find_widget ~118

Search for widgets by class, objectName, text content, or visibility. Returns a list of matching widgets with their IDs. Examples: find_widget(class_name="QPushButton") find_widget(text="Apply Mods") find_widget(object_name="enabledCheckBox")

NameTypeReqDescription
class_name
object_name
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
text
visible
NameTypeReqDescription
resultstringyes

No examples provided.

get_app_output ~133

Get the last n lines of the launched app's real stdout/stderr: print() output, uncaught tracebacks, and Qt/console warnings. This is the app's actual console output, captured because launch_app redirects it to a log file. Use this to debug crashes or startup failures. For structured Python logging records use get_logs() instead. Only works for apps started via launch_app on this server.

NameTypeReqDescription
ninteger
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

get_app_state ~65

Get app-level state: active window, focused widget, screen info. Useful to understand focus before sending keyboard events.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

get_app_status ~86

Report combined health of a launched app: whether the process is alive, its exit code, whether the bridge responds, and whether the main thread is likely blocked by a modal dialog (process alive but bridge unresponsive).

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

get_launch_help ~47

Return how to call launch_app — especially the script parameter. Call this before launch_app when you are unsure which entry .py to use or whether script should include a subfolder path.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

get_logs ~74

Get the last n log messages captured from the app's Python logging system. Includes timestamp, level, logger name, and message.

NameTypeReqDescription
ninteger
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

get_widget_info ~75

Get detailed properties and state of a specific widget. Includes geometry, text, enabled/visible state, and dynamic Qt properties.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
widget_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_widget_tree ~85

Get the full widget hierarchy of all visible windows as JSON. Each widget has: id, class, object_name, visible, enabled, geometry, text, children. Use widget IDs from this tree in other tools.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

launch_app ~239

Launch a PySide6 app with the MCP bridge injected, then wait until the UI is ready.

NameTypeReqDescription
app_argsOptional CLI arguments forwarded to the script, e.g. ['--verbose'].
commandDEPRECATED — ignored. Do not use. Older MCP schemas listed this as required; pass cwd instead.
cwdstringyesREQUIRED. Absolute path to the PySide6 project root — the folder that contains pyproject.toml (same directory you would cd into before running the app). Example: C:/dev/my-app or /home/dev/my-app
scriptstringEntry .py path RELATIVE to cwd (not absolute). Default: main.py. Omit or keep default when main.py is at project root. Use script='app.py' if the entry has another name at root. Use script='src/run.p…
timeoutintegerSeconds to wait for UI readiness. Default 45; use 60–90 for cold starts.
NameTypeReqDescription
resultstringyes

No examples provided.

list_actions ~70

List all QActions (menu items, toolbar actions) in visible windows with their name, text, shortcut, and enabled/checked state.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

list_apps ~36

List apps launched by this MCP server. Each entry is {pid}. Pass pid= to other tools when more than one app is running.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

press_key ~125

Press a key on the currently focused widget. Named keys: enter, return, escape, tab, backtab, backspace, delete, up, down, left, right, space, home, end, pageup, pagedown, f1–f6 Single characters: pass the character directly, e.g. 'a', 'A', '1'

NameTypeReqDescription
keystringyes
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

screenshot ~80

Capture a screenshot of the app window (or a specific widget by ID). Returns the image so you can see the current UI state. Call this first to orient yourself.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
widget_id

No output schema declared.

No examples provided.

scroll ~102

Scroll a widget. dy > 0 scrolls down, dy < 0 scrolls up. dx: horizontal scroll (positive = right). widget_id: target widget; omit to scroll the main window.

NameTypeReqDescription
dxinteger
dyintegeryes
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
widget_id
NameTypeReqDescription
resultstringyes

No examples provided.

stop_app ~62

Stop a previously launched app (started via launch_app). Omit pid to stop the last launched app.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
NameTypeReqDescription
resultstringyes

No examples provided.

trigger_action ~96

Trigger a QAction directly by objectName (`name`) or visible label (`text`), without clicking through menus. Useful to avoid opening modal menus and to reach toolbar/menu actions reliably. Provide at least one of name/text.

NameTypeReqDescription
name
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
text
NameTypeReqDescription
resultstringyes

No examples provided.

type_text ~79

Type text into a widget (focuses it first) or the currently focused widget. For special characters use press_key instead.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
textstringyes
widget_id
NameTypeReqDescription
resultstringyes

No examples provided.

wait_for_idle ~107

Wait until the app's UI has been quiet (no layout/paint activity) for `quiet_ms` ms, or until `timeout` seconds elapse. Call after a click or action that triggers async work, before taking a screenshot.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
quiet_msinteger
timeoutnumber
NameTypeReqDescription
resultstringyes

No examples provided.

wait_until_ready ~120

Wait until the app UI is ready: a visible top-level window that has been quiet (no layout/paint activity) for `quiet_ms` milliseconds. Use after an action that reloads or rebuilds the UI. Returns the readiness snapshot. Does not launch anything — the app must already be running.

NameTypeReqDescription
pidApp pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
quiet_msinteger
timeoutinteger
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the PySide6 MCP server?

PySide6 MCP is listed in the public MCP registry as io.github.com55/pyside6-mcp. Playwright-style MCP to inspect, control, and debug PySide6 desktop GUIs. This page covers its PyPI package (pyside6-mcp).

Is the PySide6 MCP server safe to use?

PySide6 MCP scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PySide6 MCP server expose?

PySide6 MCP exposes 22 tools: screenshot, get_widget_tree, get_widget_info, get_app_state, find_widget, and 17 more. Their descriptions and schemas cost roughly 2,139 tokens of context every time the server is loaded.

Is the PySide6 MCP server still maintained?

PySide6 MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the PySide6 MCP server under?

PySide6 MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.