WPFVisualTreeMcp vs Glass

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
🖥️ OS Automation
G
Glass
fixed-width
🖥️ OS Automation
Summary⃣ 🏠 🪟 - Inspect, debug and drive running WPF (.NET desktop) apps: visual tree, dependency properties, data bindings and binding errors, DataContext, and screenshots with open popups/menus included, plus clicking, item selection, text input and keyboard shortcuts. Auto-injects into any running WPF process (x64/x86) with no source changes. dotnet tool install -g WpfVisualTreeMcpGives a coding agent a build → see → interact → debug loop over the native GUI app it is writing: launch the app, screenshot it, read its accessibility tree, inject mouse/keyboard/gestures, tail its logs, and diff frames to confirm a change landed. Drives apps as an external black box with no app integration, so any toolkit or language works. 30 tools with text-first responses (element ids, diffs, waits) so the agent need not screenshot every step, plus optional sandboxing of the launched app. Backends: X11, Wayland, Windows, macOS, Android emulators, and the iOS Simulator.
Quality signal27/100 (Emerging)27/100 (Emerging)
Install pathnpx · lownpx · low
Engagement 0 0 0 9 0 0 0 10
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView WPFVisualTreeMcpView Glass
More alternatives to WPFVisualTreeMcpMore alternatives to GlassOS Automation category

Other servers like WPFVisualTreeMcp