Skip to main content
Glama
faze79

WpfVisualTreeMcp

by faze79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to WpfVisualTreeMcp

No user-submitted related servers found.

    Related Servers

    • netcoredbg-mcp

      thebtf
      A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to debug .NET applications with breakpoints, stepping, variable inspection, and GUI automation for WPF, WinForms, and Avalonia apps.
      135
      72 PyPI
      7
      MIT

    • Netwright

      ricfanin
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to launch, inspect, and operate WPF, WinForms, and WinUI desktop applications through UI Automation, with compact snapshots, background actions, state verification, and export to regression tests.
      16
      MIT

    • screen-use

      tongriyaotxt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      3
      MIT

    • windows-gui-mcp

      dcl632
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      28 PyPI
      2
      MIT

    • mcp-test-utils

      JeenyJAI
      F
      license
      Not graded
      quality
      B
      maintenance
      Desktop UI automation for AI agents: screenshots, window management, mouse, keyboard, UI Automation tree, OCR. Single Windows x64 binary, no dependencies.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 28 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources