
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher

A Windows UI Automation MCP Server for WPF, WinUI, Avalonia & WinForms UIInspect.MCP is a MCP server that gives AI agents and developer tools semantic access to Windows desktop applications. Instead of brittle pixel‑based automation, UIInspect.MCP exposes a rich, structured view of the UI
UIInspect.MCP.Server is a consent-gated NuGet MCP server that gives AI agents semantic access to Windows applications through UI Automation 3 (UIA3). It discovers accessible application windows, returns bounded control trees, and performs deterministic actions against opaque element references instead of relying on screenshots or pixel coordinates.
The package runs as a local stdio server on .NET 10. WPF, WinForms, WinUI 3, Avalonia, and .NET MAUI Windows are directly tested against deterministic UI Automation fixtures.
Once the package is available on NuGet.org, click to install it in your preferred environment:
Note:
UIInspect.MCP.Server and select the latest 0.* prerelease.--source <feed-path> to the dnx arguments.Manual MCP configuration using NuGet:
{
"mcpServers": {
"uiinspect-mcp": {
"type": "stdio",
"command": "dnx",
"args": [
"[email protected]",
"--prerelease",
"--yes"
]
}
}
}
Some clients use servers instead of mcpServers; only the outer property name changes.
The NUKE build stamps every literal UIInspect.MCP.Server package coordinate in this README with the MinVer package version before packaging:
dnx [email protected] --yes
Start the server with uiinspect-mcp --unrestricted, or set UIINSPECT_UNRESTRICTED=true in its MCP server environment and restart it. For dnx, pass the server option after -- (for example, append -- --unrestricted to the command above).
This explicit server-owner configuration enables all inspection, interaction and logical keyboard capabilities for the server lifetime. Agents can discover and attach directly without requesting consent. There are no UIInspect approval dialogs, consent expiry, broker IPC or operation rate limits in this mode. uiinspect_get_unattended_approval reports an authorization expiry of DateTimeOffset.MaxValue. Stop the server and remove the startup option or environment variable to disable it; no MCP tool can enable this mode.
Exact process identity checks, per-client session ownership, bounded tree responses, stale-element detection and audit records remain active. Prefer semantic operations to minimize foreground and cursor disruption. Keyboard and physical-click fallbacks may still require focus. Host application MCP approval prompts are controlled by that host's configuration and cannot be disabled by this server. The default startup continues to use the existing Windows approval policy.
For Codex, configure its separate server tool policy as well:
[mcp_servers.uiinspect-mcp]
command = "uiinspect-mcp"
args = ["--unrestricted"]
default_tools_approval_mode = "approve"
Use a package version containing unrestricted startup support, or point the command at a locally built server. Restart the MCP connection after changing configuration. Codex documents its host policy separately in the MCP configuration reference.
The package includes the uiinspect Codex skill and its MCP dependency metadata. When the packaged server starts, it installs missing skill files into an existing Codex home: CODEX_HOME when it is set and exists, otherwise %USERPROFILE%\.codex when that directory exists. Automatic installation never overwrites existing skill files.
Install the skill explicitly and create the Codex home when needed. This command installs the skill and exits without starting the MCP server:
dnx [email protected] --yes -- --install-codex-skill
To deliberately replace an existing installed copy with the packaged version:
dnx [email protected] --yes -- --install-codex-skill --force
Set CODEX_HOME before either command when Codex uses a non-default location. The skill is installed at <Codex home>\skills\uiinspect.
Invoke the installed skill with a request such as:
Use $uiinspect to inspect and safely operate the target Windows application.
dnx.The MCP protocol owns stdout; server diagnostics are written to stderr.
The current package deliberately does not provide XAML source or visual trees, dependency properties, bindings, validation, DataContext or command diagnostics, hot reload, screenshots, OCR, overlays, recording/replay, arbitrary reflection, shell execution, generic property writes, or TCP transport.
UIInspect never treats an agent name or ordinary MCP request as user approval. Stdio client metadata is self-asserted and cannot prove that the caller is Codex, Claude Code, or another trusted agent, so UIInspect does not provide an agent-name bypass. In normal mode, the local user approves the exact process instance and requested capabilities in a trusted Windows dialog before the server attaches. Repeated and concurrent requests reuse that server-session decision without opening another dialog. A denial is terminal for that client and process instance until the server restarts, and later capability expansion is denied rather than silently approved or prompted again.
Inspection, interaction, and keyboard access are separate capabilities. Request only the minimum needed for the task. Grants are short-lived and bound to the local stdio server principal, exact process identity, Windows session, and approved capabilities. Tool parameters cannot supply or override that principal.
For unattended tests and multiple agent sessions, activate one fixed-duration approval from a trusted interactive terminal:
uiinspect-mcp --authorize-unattended 8
uiinspect-mcp --unattended-status
uiinspect-mcp --revoke-unattended
Replace 8 with exactly 1, 2, 5, 8, 12, or 24. When invoking the NuGet package directly, append manager arguments to the existing dnx command after --, for example -- --authorize-unattended 8.
The trusted dialog clearly approves all local UIInspect clients in the current Windows user and interactive session for Inspect, Interact, and Keyboard. The broker keeps the lease only in memory, serves concurrent agent sessions through current-user-only named pipes, and stops at expiry, revocation, process exit, logoff, or reboot. Each agent calls uiinspect_get_unattended_approval, then follows the normal consent and attach workflow; uiinspect_request_consent exchanges the broker lease for an exact-process grant without another dialog. Activation and extension are deliberately not MCP tools.
Successful actions invalidate all current element references. Re-inspect before the next action so the server can semantically resolve the current UI rather than act on stale coordinates.
The default audit file is:
%LOCALAPPDATA%\UIInspect.MCP\audit\actions.jsonl
Set UIINSPECT_AUDIT_PATH for the MCP server process to use another location. Audit records exclude entered values, password content, clipboard data, screenshots, raw provider exceptions, and all keystrokes except the allowlisted logical key name. Appends are enforced at the application level; protect the audit directory with an ACL that grants access only to the server account and administrators.
See the complete security model for consent scopes, rate limits, audit contents, integrity boundaries, and the threat model.
uiinspect_get_unattended_approval when an unattended window is expected, then call uiinspect_discover_windows.uiinspect_request_consent once with every capability required for the session. An active broker lease avoids a per-target dialog; otherwise the local user must approve the exact process instance. Repeats reuse the decision and cannot expand it.uiinspect_attach.uiinspect_inspect_tree with the smallest useful depth and node budget.uiinspect_invoke, uiinspect_set_value (or its uiinspect_set_text alias), uiinspect_select_item, or uiinspect_expand_collapse. Use uiinspect_click only when the provider does not expose InvokePattern, and use uiinspect_send_key only when keyboard consent was granted.uiinspect_close_session.stale_element, inspect again and use a newly returned element reference.unattended_approval_inactive, ask the user to activate a window from a trusted terminal or continue with the ordinary per-target prompt. Do not loop on the status tool.consent_expired, call uiinspect_get_unattended_approval when unattended operation is expected, then call uiinspect_request_consent, uiinspect_attach, and uiinspect_inspect_tree. A still-active broker lease or retained explicit decision renews the exact-process grant without another dialog.session_not_found, attach again when consent remains active; otherwise request consent, attach, and inspect.target_changed or target_unavailable, rediscover the target; a new exact process identity requires its own consent decision.rate_limited, wait for retryAfterMilliseconds before retrying.consent_denied as terminal for that client, target, and server process. Do not retry in a loop.pattern_not_supported as a semantic limitation; select another supported operation rather than falling back to blind input.The NuGet package contains:
uiinspect-mcp .NET tool and its runtime dependencies..mcp/server.json MCP registry metadata.skills/uiinspect skill, including SKILL.md and agents/openai.yaml.The package uses ModelContextProtocol 2.1.0 and FlaUI 5.0 with UIA3.
A Windows UI Automation MCP Server for WPF, WinUI, Avalonia & WinForms UIInspect.MCP is a MCP server that gives AI agents and developer tools semantic access to Windows desktop applications. Instead o
Overview
A Windows UI Automation MCP Server for WPF, WinUI, Avalonia & WinForms UIInspect.MCP is a MCP server that gives AI agents and developer tools semantic access to Windows desktop applications. Instead of brittle pixel‑based automation, UIInspect.MCP exposes a rich, structured view of the UI
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
UIInspect.MCP runs locally over stdio.
Last checked 2026-10-28. A Windows UI Automation MCP Server for WPF, WinUI, Avalonia & WinForms UIInspect.MCP is a MCP server that gives AI agents and developer tools semantic access to Windows desktop applications. Instead of brittle pixel‑based automation, UIInspect.MCP exposes a rich, structured view of the UI