Qt Ui Inspector logo

Qt Ui Inspector

Organization
dcc-mcp
qt-ui-inspector

Infrastructure skill — DCC-agnostic Qt UI introspection: list top-level windows, find widgets by name/class, describe widget properties, walk the widget tree, and poll for availability. Works in any DCC with a Qt binding (Maya, Blender, Houdini, Unreal, etc.). All tools are read-only and lazy-loaded.

Overview

Publisherdcc-mcp
Repositorydcc-mcp-core
Skill nameqt-ui-inspector
Stars
74
Forks
7
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by dcc-mcp on GitHub. Read the source before you install it.

Installation

Install the Qt Ui Inspector AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dcc-mcp/dcc-mcp-core/tree/main/python/dcc_mcp_core/skills/qt-ui-inspector
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-core.git /tmp/dcc-mcp-core
mkdir -p .claude/skills
cp -r /tmp/dcc-mcp-core/python/dcc_mcp_core/skills/qt-ui-inspector .claude/skills/qt-ui-inspector
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qt Ui Inspector in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Qt Ui Inspector on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Qt Ui Inspector is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Qt UI Inspector

Cross-DCC Qt UI introspection tools. All tools lazy-import the host's Qt binding (qtpy, PySide6, PySide2, PyQt6, or PyQt5).

Tools

dcc_qt_ui_inspector__list_windows

List every top-level Qt window with object name, class, visibility, geometry, and child count.

dcc_qt_ui_inspector__find_widgets

Locate Qt widgets by object name (exact/substring/regex), class name, and visibility. Bounded result count.

dcc_qt_ui_inspector__describe_widget

Return a single Qt widget's structured state - class, geometry, flags, accessible name/description, and bounded property snapshot.

dcc_qt_ui_inspector__snapshot_tree

Walk the Qt widget tree under a root and return it as a JSON-safe tree with depth and node-count budgets.

dcc_qt_ui_inspector__wait_for_widget

Poll for a Qt widget by name/class with visible/enabled gates and bounded timeout.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Qt Ui Inspector AI skill do?

Infrastructure skill — DCC-agnostic Qt UI introspection: list top-level windows, find widgets by name/class, describe widget properties, walk the widget tree, and poll for availability. Works in any DCC with a Qt binding (Maya, Blender, Houdini, Unreal, etc.). All tools are read-only and lazy-loaded.

Why use Qt Ui Inspector on TypingMind?

Because you install it once and use it with any model. Qt Ui Inspector is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Qt Ui Inspector in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dcc-mcp/dcc-mcp-core/tree/main/python/dcc_mcp_core/skills/qt-ui-inspector. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Qt Ui Inspector?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Qt Ui Inspector?

As many as you like. As long as a model supports skills, you can use Qt Ui Inspector with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Qt Ui Inspector AI skill free?

Yes. It is published on GitHub by dcc-mcp under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇