mc-iclone8-ui-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ui.inspect_applicationA | Inspecte les fenêtres visibles iClone 8 en lecture seule. |
| ui.inspect_accessibility_treeB | Lit les contrôles directs Windows UI Automation sans effectuer d'action. |
| ui.capture_screenB | Capture l'écran ou la fenêtre iClone 8 sans modifier la scène. |
| scene.read_visible_stateB | Lit l'état visible connu de l'interface iClone 8. |
| workflow.stop_allB | Demande l'arrêt propre du workflow UI courant. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect: screen capture, visible state reading, workflow control, application inspection, and accessibility tree inspection. No ambiguity exists between their purposes.
All tool names follow a consistent pattern: <scope>.<action> with snake_case action names (e.g., ui.capture_screen, scene.read_visible_state).
With 5 tools covering capture, state, workflow, and inspection, the count is well-scoped for a UI monitoring server.
Covers capture, state reading, and two inspection methods, plus workflow stop. Missing tools for starting workflows or retrieving detailed element properties, but serves its monitoring purpose adequately.