Clara Windows 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 |
|---|---|
| list_windowsA | List visible top-level windows with HWND, title, process info, bounds, and foreground state. |
| get_foreground_windowB | Get the current foreground window. |
| focus_windowB | Bring a target window to the foreground by HWND or partial title match. |
| capture_screenB | Capture the desktop or a specific window to a PNG file. |
| move_mouseC | Move the mouse cursor to an absolute screen coordinate. |
| click_mouseC | Click at a screen coordinate using the selected mouse button. |
| press_keyB | Send a key sequence through SendKeys syntax, for example {ENTER} or ^a. |
| type_textB | Type text through SendKeys with special characters escaped. |
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 8 tools
Each tool targets a distinct action: listing windows, getting foreground, focusing, capturing, mouse movement/click, and keyboard input. No overlap in purpose, unambiguous.
All tool names follow a consistent verb_noun pattern (list_windows, get_foreground_window, capture_screen, etc.) with snake_case, perfectly predictable.
8 tools is well-scoped for a Windows UI automation server, covering window management, screen capture, and input simulation without bloat or thinning.
The set covers core UI automation workflows (window handling, mouse/keyboard input, screenshot). Minor gaps like reading window properties or mouse scroll are not critical but could be added.