Ext Ops Panel
Open dashboard
Comparison

io.github.faze79/wpf-visual-tree vs UIAutomationMcp

io.github.faze79/wpf-visual-tree is an MCP server published by faze79. Marketplaces we read that list it: 1 (Official MCP Registry). UIAutomationMcp is an MCP server published by trsdn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.faze79/wpf-visual-treeUIAutomationMcp
Official MCP Registry Listed
Version: 0.20.0
Forks (GitHub): 8
Stars (GitHub): 20
Not marked · First seen
Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.faze79/wpf-visual-tree vs UIAutomationMcp
Factio.github.faze79/wpf-visual-treeUIAutomationMcp
Marketplaces that list it11
Stars (GitHub) (differs)20 (better)4 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last release (differs)2026-10-25Not published
Where it runs (differs)On your machine (WpfVisualTreeMcp)On your machine (UIAutomationMcp.McpServer)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/faze79/wpfvisualtreemcpgithub.com/trsdn/mcp-server-uiautomation
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.faze79/wpf-visual-tree

In its own words, on Official MCP Registry:

Inspect and drive WPF apps: trees, bindings, screenshots, mouse dragging and touch gestures.

UIAutomationMcp

In its own words, on Official MCP Registry:

Windows UI Automation MCP server for desktop inspection and element lookup. Windows only.

How to run each

io.github.faze79/wpf-visual-tree

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

UIAutomationMcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.faze79/wpf-visual-tree · What it can do: UIAutomationMcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built