codex-cua-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_windowsB | List all open windows that can be controlled |
| list_appsA | List installed apps with their open windows |
| get_windowB | Rehydrate a window object by id (useful after losing window binding) |
| launch_appC | Launch an application |
| activate_windowC | Bring a window to the foreground |
| get_window_stateA | Capture screenshot and/or accessibility tree of a window. Call this before input actions. |
| clickC | Click at coordinates or on an element in a window |
| type_textC | Type text into the current focus of a window |
| press_keyB | Press a keyboard key or chord (e.g., 'Return', 'Control_L+a') |
| scrollC | Scroll at coordinates in a window |
| dragC | Drag from one coordinate to another in a window |
| set_valueC | Set the value of an editable element |
| perform_secondary_actionC | Perform a secondary action on an element (e.g., right-click menu, expand) |
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 13 tools
Each tool has a clearly distinct purpose: window management, input actions, app launching, and element manipulation. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores (e.g., activate_window, get_window_state). No mixing of styles or irregular naming.
13 tools cover a well-scoped set of GUI automation operations (window control, input, app management), neither too few nor excessive for the domain.
The tool surface covers core actions (launch, list, navigate, input, state capture). Minor gaps like explicit screenshot-only or element waiting could exist but the set is largely complete for typical workflows.