WpfVisualTreeMcp
Related Servers
Alternatives to WpfVisualTreeMcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to debug .NET applications with breakpoints, stepping, variable inspection, and GUI automation for WPF, WinForms, and Avalonia apps.1356MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to see, locate UI elements, and operate any Windows desktop app through natural language, using accessibility-tree matching with optional vision-model fallback, plus an autonomous visual loop with introspection and meta-learning.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to automate Windows desktop applications through semantic UI Automation instead of brittle coordinate clicks, with tools for discovering windows, finding controls by stable identifiers, and verifying actions.1MIT
- FlicenseNot gradedqualityCmaintenanceDesktop UI automation for AI agents: screenshots, window management, mouse, keyboard, UI Automation tree, OCR. Single Windows x64 binary, no dependencies.-
- AlicenseNot gradedqualityBmaintenanceAn MCP server for inspecting and controlling running XAML applications across Avalonia, WPF, WinUI 3, and .NET MAUI, enabling AI clients to walk trees, modify properties, take screenshots, and send input.26Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that gives AI assistants full control over native Windows applications — launch, inspect, click, type, screenshot, and test any WinUI3, WPF, WinForms, UWP, or Win32 app.44 npm39MIT
TDQS
Scored across 28 tools
Most tools clearly target distinct operations: querying, inspecting, mutating, capturing, and diagnosing. The intentional wpf_find_elements/wpf_find_elements_deep pair and the diagnostic cluster around get_bindings, evaluate_binding, get_data_context, and explain_triggers have some boundary overlap, but the descriptions provide enough direction to avoid serious mis-selection.
All tools use the wpf_ namespace and almost all follow a predictable lower_snake verb_noun convention such as wpf_get_visual_tree, wpf_click_element, and wpf_clear_binding_errors. The few exceptions like wpf_attach, wpf_snapshot, and wpf_diff are still concise and do not break the overall pattern.
28 tools is on the heavy side and exceeds the typical comfortable range, but the broad WPF domain justifies much of the surface area: process attachment, tree querying, binding/style/resource inspection, UI actions, capture/diff, and live editing. A few tools could be consolidated, but most earn their place.
The tool set covers the full inspect-modify-verify loop: attach/discover, find/wait, read properties and bindings, perform UI actions, edit and revert properties, snapshot/diff/screenshot, and diagnose binding errors. Minor gaps such as a generic scroll/focus helper or general UIA pattern invocation exist, but core workflows are not blocked.