Ext Ops Panel
Open dashboard
Comparison

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

vibesurfer is a plugin bundle for AI coding tools published by frane. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-14. 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
Marketplacevibesurferio.github.faze79/wpf-visual-tree
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 16
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

vibesurfer vs io.github.faze79/wpf-visual-tree
Factvibesurferio.github.faze79/wpf-visual-tree
Marketplaces that list it11
Stars (GitHub) (differs)16 (worse)17 (better)
Forks (GitHub) (differs)0 (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
Parts of the bundle (differs)3Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/frane/vibesurfergithub.com/faze79/wpfvisualtreemcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

vibesurfer

In its own words, on Claude Code: claude-plugins-community:

A real browser for your local AI agent. Native WebKit on macOS, WebKitGTK on Linux, WebView2 on Windows, with a wire protocol designed for LLMs instead of for humans staring at DevTools. Login once, scrape JS-rendered pages, fill forms, take screenshots, drive your own app for smoke tests.

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

vibesurfer As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibesurfer@claude-community

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

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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