pyside6-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshotA | 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. |
| get_widget_treeA | 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. |
| get_widget_infoA | Get detailed properties and state of a specific widget. Includes geometry, text, enabled/visible state, and dynamic Qt properties. |
| get_app_stateA | Get app-level state: active window, focused widget, screen info. Useful to understand focus before sending keyboard events. |
| find_widgetA | 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") |
| clickA | Click a widget or screen coordinate.
|
| double_clickB | Double-click a widget. Sends two rapid left-clicks. |
| type_textA | Type text into a widget (focuses it first) or the currently focused widget. For special characters use press_key instead. |
| press_keyA | 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' |
| scrollA | 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. |
| get_logsB | Get the last n log messages captured from the app's Python logging system. Includes timestamp, level, logger name, and message. |
| get_app_outputA | 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. |
| eval_pythonA | Evaluate a Python expression or execute a statement inside the app process. Context provides:
|
| get_launch_helpA | 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. |
| launch_appA | Launch a PySide6 app with the MCP bridge injected, then wait until the UI is ready. |
| wait_until_readyA | Wait until the app UI is ready: a visible top-level window that has been
quiet (no layout/paint activity) for Use after an action that reloads or rebuilds the UI. Returns the readiness snapshot. Does not launch anything — the app must already be running. |
| wait_for_idleA | Wait until the app's UI has been quiet (no layout/paint activity) for
|
| get_app_statusA | 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). |
| list_actionsA | List all QActions (menu items, toolbar actions) in visible windows with their name, text, shortcut, and enabled/checked state. |
| trigger_actionA | Trigger a QAction directly by objectName ( |
| list_appsA | List apps launched by this MCP server. Each entry is {pid}. Pass pid= to other tools when more than one app is running. |
| stop_appA | Stop a previously launched app (started via launch_app). Omit pid to stop the last launched app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/com55/pyside6-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server