Ext Ops Panel
Open dashboard
Comparison

wpf-dev-pack vs io.github.faze79/wpf-visual-tree

wpf-dev-pack is a plugin bundle for AI coding tools published by vincent lee. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.faze79/wpf-visual-tree is an MCP server published by faze79. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacewpf-dev-packio.github.faze79/wpf-visual-tree
Community marketplace christian289/dotnet-with-claudecode Listed
Version: 1.8.1
Forks (GitHub): 6
Stars (GitHub): 41
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.0
Forks (GitHub): 7
Stars (GitHub): 17
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

wpf-dev-pack vs io.github.faze79/wpf-visual-tree
Factwpf-dev-packio.github.faze79/wpf-visual-tree
Marketplaces that list it11
Stars (GitHub) (differs)41 (better)17 (worse)
Forks (GitHub) (differs)6 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (WpfVisualTreeMcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)16Not published
Parts of the bundle (differs)45Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/christian289/dotnet-with-claudecodegithub.com/faze79/wpfvisualtreemcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-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

wpf-dev-pack

In its own words, on Community GitHub marketplaces:

WPF development toolkit with 57 skills, 9 agents, and 5 commands for CustomControl, MVVM, XAML styling, and high-performance rendering

io.github.faze79/wpf-visual-tree

In its own words, on Official MCP Registry:

Let AI agents inspect and drive running WPF apps: tree, bindings, screenshots, clicks, text input.

How to run each

wpf-dev-pack As a Claude Code plugin

Claude Code
/plugin marketplace add christian289/dotnet-with-claudecode
/plugin install wpf-dev-pack@dotnet-claude-plugins

io.github.faze79/wpf-visual-tree

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: wpf-dev-pack · What it can do: io.github.faze79/wpf-visual-tree · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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