WpfVisualTreeMcp

Let AI agents see, debug and drive running WPF apps. Snoop + Playwright for AI, exposed over the Model Context Protocol β visual tree, bindings, screenshots, mouse dragging, touch gestures, text input and keyboard. Inspect running apps without source changes; touch behavior depends on the application's input support.

Drag-and-drop, move a canvas item, tap, hold, pan, pinch to zoom and rotate β then query controls, fill a form, select an item and diagnose a binding error. The gesture sequence records real WPF input through MCP, targets controls by AutomationId and checks the application's response, just like the automated tests.
Watch the animated demo directly.
New in v0.20.0:
Verified support for WPF on .NET 9, .NET 10 and .NET Framework 4.8.1, on both
x86 and x64. CI exercises automatic injection and self-hosting across all six
supported target frameworks, plus the installed C# SDK from .NET 8, 9 and 10 test
projects. The x86 injection helper can also use .NET 9 or 10 when .NET 8 is absent.
The WpfVisualTreeMcp.Automation C# SDK
drives virtualized DataGrids/TreeViews, waits for controls, manages WPF windows and
streams property changes. The 38-tool MCP server and CLI share the inspection and
input engine, including direct AutomationId targeting.
Workflow recording/replay/xUnit export, aggregate diagnostics, full-content screenshots
and .NET Framework 4.7.2 support remain available from v0.16.0. Thanks to @miloszkukla
for the compatibility and screenshot work in PR #22.
Quickstart (60 seconds)
- Download and extract
WpfVisualTreeMcp-vX.Y.Z-win-x64.zip from the latest release (requires a .NET 8, 9 or 10 Desktop Runtime).
- Register it in your MCP client β for Claude Code, add to
.mcp.json:
{
"mcpServers": {
"wpf-visual-tree": {
"command": "C:/path/to/WpfVisualTreeMcp.Server.exe",
"args": []
}
}
}
- Ask your agent: "Look at my running WPF app and tell me why the Save button is disabled."
Prefer the terminal? The same exe is a full CLI: WpfVisualTreeMcp.Server.exe help.
From v0.14.0, run wpfinspect update (or WpfVisualTreeMcp.Server.exe update)
to update the installation you launched. See updating.
Using Codex? Follow the plugin installation to install the MCP
configuration and skill together.
C# test SDK
WpfVisualTreeMcp.Automation exposes the inspection and input engine as C# objects,
with direct process attachment and AutomationId locators. The package includes the
injection payload and works without starting an MCP server or CLI.
| Component | Supported frameworks |
|---|
| WPF application being automated | .NET Framework 4.7.2, 4.8, 4.8.1; .NET 8, 9, 10 |
| C# project consuming the Automation NuGet | .NET 8, 9, 10 |
| Architectures | Windows x86 and x64; use an x64 test process to control either |
The application and test project can use different frameworks: for example, a
.NET 10 test can automate a .NET Framework 4.8.1 application. The SDK's net8.0
library works in .NET 9/10 test projects; it is not a .NET Framework test library.
The compatibility matrix is exercised before
release, including actual runtime-version checks. Framework 4.x target builds run
on the installed 4.8.1 runtime, since those runtimes update in place.
dotnet add package WpfVisualTreeMcp.Automation --version 0.20.0
using WpfVisualTreeMcp.Automation;
await using var app = await WpfApplication.AttachAsync(processId);
await app.ByAutomationId("LoadButton").ClickAsync();
await app.ByAutomationId("StatusTextBox").WaitForTextAsync(
"loaded", timeout: TimeSpan.FromSeconds(30));
await app.ByAutomationId("Canvas").PanAsync(100, 0);
await app.ByAutomationId("Canvas").ZoomAsync(1.5);
Text waits compare the exact property value: not loaded does not match loaded.
Timeouts throw with the expected and last observed values. Property predicates,
cancellation, drag, touch, assertions, inspection and recording/replay are also
available. Attached sessions leave the app running on disposal; launched sessions
own and clean up their process by default.
await app.ByAutomationId("Orders").AsDataGrid()
.RowByKey("Id", "42").Cell("Quantity").SetTextAsync("7");
await app.ByAutomationId("Folders").AsTreeView().Node("Projects", "WPF").SelectAsync();
await app.ByAutomationId("Enabled").CheckAsync();
await using var changes = await app.ByAutomationId("StatusTextBox").ObservePropertyAsync("Text");
The SDK is a separate package from the MCP tool WpfVisualTreeMcp.
See installation, API examples and requirements.
Overview
WpfVisualTreeMcp is a Model Context Protocol (MCP) server that allows AI coding agents (Codex, Claude Code, Cursor, GitHub Copilot) to inspect and interact with running WPF applications. Think of it as giving your AI assistant the same capabilities as tools like Snoop WPF or Visual Studio's Live Visual Tree.
Why This Matters
Debugging WPF UI issues traditionally requires manual inspection with specialized tools. This project bridges that gap by exposing WPF inspection capabilities through MCP, enabling AI agents to:
- Understand UI structure during code reviews
- Diagnose binding errors automatically
- Suggest fixes for layout issues
- Assist with UI refactoring tasks
- Analyze visual tree hierarchies in real-time
Features
Core Inspection
- Process Discovery - List all running WPF applications available for inspection
- Visual Tree Navigation - Traverse the complete visual tree hierarchy
- Logical Tree Access - Navigate the logical tree structure
- Property Inspection - Read all dependency properties of any UI element
Binding & Resources
- Binding Analysis - Inspect bindings with converter, StringFormat, FallbackValue, MultiBinding support
- DataContext Inspection - View DataContext type, properties, INPC status, and inheritance chain
- Binding Error Detection - Automatically capture and report binding errors with classification
- Resource Enumeration - Browse resource dictionaries at any scope
- Style Inspection - View applied styles and templates
Search & Monitoring
- Element Search - Find elements by type, name, or property values
- Deep Search - Search entire tree including AdornerLayer and Popup elements
- Property Watching - Monitor property changes in real-time
Interaction & Export
- Touch Gestures (v0.13.0) -
wpf_touch_gesture / CLI touch: native tap, long press, swipe, pinch and rotation with one or two contacts. Includes an interactive demo and WPF compatibility guidance.
- Mouse Drag -
wpf_drag / CLI drag: drag between visual-tree elements or by a local displacement, with left/right/middle buttons, configurable duration and local start/end points. Supports slider thumbs, splitters and drag-and-drop. See the parameters and examples.
- Screenshot Capture - Current source uses
auto capture for native hosted content and reports the selected mode; explicit render rejects unsupported native areas. Capture window/element screenshots visible to AI agents; full_content=true / CLI --full-content captures scrollable content, including virtualized lists, and restores the original scroll position
- Element Highlighting - Visually highlight elements in the running app
- Control Click (v0.4.0) - Click elements via UI Automation (
Invoke/Toggle/Select/ExpandCollapse) or a real OS mouse click
- Set Text (new in v0.5.0) - Fill a TextBox/ComboBox/PasswordBox via UI Automation
IValueProvider.SetValue, with a TextBox.Text / PasswordBox.Password / reflected-Text fallback, or physical=true to type via OS keyboard input (full Unicode BMP)
- Send Keys (new in v0.5.0) - Send keyboard shortcuts (
Ctrl+S, Alt+F4, F5, Enter, Ctrl+Shift+F, ...) to an element or the focused window via OS keyboard input
- Layout Information - Get detailed layout metrics
- Tree Export - Export visual tree to XAML or JSON format
- Auto-Injection - Inject Inspector into running WPF processes (no source changes needed); multi-architecture since v0.6.0 β a 64-bit server can inject into 32-bit WPF apps via a bundled
WpfInjectorHelper.exe
Dual-Mode CLI (new in v0.4.0)
The same WpfVisualTreeMcp.Server.exe runs as either an MCP stdio server
(no arguments, default) or as a one-shot CLI (any recognised subcommand).
Useful when the MCP server isn't connected, for scripting, and for verifying
the pipeline manually. Run WpfVisualTreeMcp.Server.exe help for the full
command list. Output is JSON on stdout; diagnostics go to stderr.
How it compares
vs. the general tool categories:
| WpfVisualTreeMcp | Snoop | FlaUI / WinAppDriver | Generic computer-use (screenshot + mouse) |
|---|
| Consumer | AI agents (MCP) + humans (CLI) | Humans (GUI) | Test code (C#) | AI agents |
| Visual tree, dependency properties | β
| β
| β (UIA view only) | β |
| Data bindings, binding errors, DataContext | β
| β
| β | β |
| Find controls by visible text / properties | β
| manual | partial (UIA) | pixel guessing |
| Click / type / select / shortcuts | β
| β | β
| β
(blind) |
| Wait for UI conditions (no sleep loops) | β
| β | β
| β |
| Element screenshots + popup-aware screen capture | β
| β | partial | full screen only |
| Works without target source changes | β
(auto-injection) | β
| β
| β
|
vs. other WPF MCP servers. Most WPF MCP servers are built on UI Automation (FlaUI): they read the accessibility tree, and can only reach WPF internals β bindings, DataContext, ViewModel state β if you install their in-process probe into the app you want to inspect. This server takes the Snoop route instead: it injects at runtime, so it reads the real visual tree and diagnoses binding errors and DataContext with zero changes to the target app β nothing to add to your build, nothing to ship into production.
| WpfVisualTreeMcp | UIA-based servers (FlaUI) | Other injection-based servers |
|---|
| Sees the real visual tree (not just the UIA view) | β
injection | β accessibility tree | β
|
| Binding errors + DataContext without a probe in the target | β
| β (needs in-process probe) | partial |
| Interaction surface | click (UIA + physical, double/right), drag, touch gestures, set-text w/ read-back, send-keys, select-item (virtualized) | click / type / select | usually invoke-only |
| Wait for element conditions | β
wpf_wait_for | β
| β |
| Popup / dropdown / context-menu screenshots | β
screen mode | partial | screenshot only |
| Cross-architecture injection (x64 β x86) | β
| n/a | β |
| Dual-mode: MCP server and one-shot CLI | β
| β | β |
| Distribution | NuGet (dnx/tool), official MCP registry, Codex plugin + skill | varies | varies |
In short: UIA-based tools see what accessibility exposes, and computer-use agents see pixels. This project gives the agent the same insider view a WPF developer has in Snoop β with no probe to install in the target app β plus the widest set of hands to act on it, over a protocol every AI coding tool speaks.
Installation
Prerequisites
- Windows 10/11
- .NET 8.0 SDK or later
- A WPF application to inspect
Building and running the complete compatibility suite requires the .NET 10 SDK,
.NET 8/9/10 Desktop runtimes for x64 and x86, and .NET Framework 4.8.1.
Installation
dotnet tool install -g WpfVisualTreeMcp
The package is also published as an MCP server package (PackageType: McpServer),
so MCP clients that support NuGet-hosted servers can launch it directly:
Option 2: Download Release
Download the latest release from GitHub Releases:
- Download
WpfVisualTreeMcp-vX.X.X-win-x64.zip
- Extract to a folder (e.g.,
C:\Tools\WpfVisualTreeMcp)
- The MCP server executable is
server/WpfVisualTreeMcp.Server.exe
Desktop extension (MCPB)
Clients that support MCP bundles can import
WpfVisualTreeMcp-v0.20.0-win-x64.mcpb.
This Windows x64 bundle includes the server runtime and a self-contained x86
injection helper. A smaller
compact bundle
provides the same tools with a reduced runtime for catalogs with upload limits.
Update either bundle through the client's extension UI. See the
MCPB guide for requirements, packaging and verification.
Option 3: Build from Source
git clone https://github.com/faze79/WpfVisualTreeMcp.git
cd WpfVisualTreeMcp
./scripts/Build-NativeBootstrapper.ps1
dotnet build -c Release
For injection build requirements, package layout, and troubleshooting, see the
Injector README. Injecting into x86 apps
requires the x86 .NET 8 runtime for the helper.
Updating
wpfinspect update --check # current/latest stable version; no installation changes
wpfinspect update # download and schedule installation automatically
wpfinspect update --status # confirm completion or inspect a failure
# For an extracted release or a published folder, invoke that exact executable:
C:\Tools\WpfVisualTreeMcp\server\WpfVisualTreeMcp.Server.exe update
update is available from v0.14.0. For an older global tool, bootstrap it once:
dotnet tool update -g WpfVisualTreeMcp
For an older portable copy, extract the latest release and use its server folder.
The command updates only the installation it was launched from. Global and
custom --tool-path tools download the exact official NuGet package, then use
dotnet tool update from that staged package (a .NET SDK is required). Temporary
NuGet download failures and publication delays receive up to four attempts, with
10, 20 and 30 seconds between attempts. If preparation fails, installed files are
unchanged; retry later. Portable folders receive the latest stable GitHub release's complete
server payload, verified against its SHA-256 digest. A source build under bin
is left to the source/build workflow; local manifest tools and dnx caches are
left to their package manager. --check explains which installation was detected.
On Windows, installation starts in a hidden worker after the CLI exits so its
executable is unlocked. A scheduled result means the worker was launched, not
that installation finished. Run update --status until it reports updated or
failed; a failed status returns exit code 1. JSON output includes the log path.
Status, logs and portable backups are stored under
%LOCALAPPDATA%\WpfVisualTreeMcp\updates, separately for each installation.
Close other MCP instances using the same files before updating. The updater does
not stop applications: occupied files cause an error, and portable replacement
failures trigger restoration from backup. Unrelated files and MCP configuration
are preserved. After success, restart the MCP client and previously inspected WPF
apps so both server and injected Inspector use the new version. Other installed
copies and any separately copied self-hosted Inspector require their own update.
Configuration
The server uses the official Microsoft/Anthropic MCP SDK for .NET, providing guaranteed compatibility with Claude Code and other MCP clients.
Claude Code
Option 1: Command Line (Recommended)
Use the claude mcp add command to add the server directly:
claude mcp add wpf-visual-tree -- C:/path/to/WpfVisualTreeMcp/publish/WpfVisualTreeMcp.Server.exe
claude mcp add --scope user wpf-visual-tree -- C:/path/to/WpfVisualTreeMcp/publish/WpfVisualTreeMcp.Server.exe
You can verify the server was added:
Option 2: Project-level JSON Configuration
Create or edit .mcp.json in your project root:
{
"mcpServers": {
"wpf-visual-tree": {
"command": "C:/path/to/WpfVisualTreeMcp/publish/WpfVisualTreeMcp.Server.exe",
"args": []
}
}
}
Option 3: Global JSON Configuration
Add to ~/.claude/settings.json:
{
"mcpServers": {
"wpf-visual-tree": {
"command": "C:/path/to/WpfVisualTreeMcp/publish/WpfVisualTreeMcp.Server.exe",
"args": []
}
}
}
Important Notes:
- Use absolute paths to the built
.exe file
- Use forward slashes (
/) in paths on Windows
- Build in Release mode for production:
dotnet build -c Release
- Restart Claude Code after configuration changes
Cursor
Add to your Cursor settings (.cursor/mcp.json):
{
"mcpServers": {
"wpf-visual-tree": {
"command": "C:/path/to/WpfVisualTreeMcp/publish/WpfVisualTreeMcp.Server.exe",
"args": []
}
}
}
Codex plugin
The repository includes a WPFVisualTreeMcp Codex plugin that installs the MCP
configuration and a wpfvisualtreemcp skill together. It runs the latest stable NuGet package,
not a build of the checked-out source. No machine-specific executable path is
required.
Prerequisites for this installation method:
- Windows 10/11 and a local Codex client with plugin support.
- .NET 10 SDK, version 10.0.300 or newer within .NET 10 for
dotnet dnx,
plus the .NET 8 runtime.
- Internet access to nuget.org on each MCP launch to resolve the latest stable
version. Downloaded packages are cached by .NET. For x86 injection, install
the x86 .NET 8 runtime as well.
From the repository root, register the local marketplace and install the plugin.
You can also download WpfVisualTreeMcp-v0.20.0-codex-plugin.zip from
GitHub Releases,
extract it, and run these commands from the extracted root:
codex plugin marketplace add .
codex plugin add wpfvisualtreemcp@WPFVisualTreeMcp
Restart Codex or open a new session, then ask it to inspect your running WPF app.
The skill can also be invoked explicitly as $wpfvisualtreemcp.
Alternatively, install directly from the upstream Git repository without cloning
it manually:
codex plugin marketplace add https://github.com/faze79/WPFVisualTreeMcp.git
codex plugin add wpfvisualtreemcp@WPFVisualTreeMcp
Use codex plugin list --marketplace WPFVisualTreeMcp to check the installation. This is
a repository marketplace; it does not imply publication in OpenAI's public
plugin directory. If your client lacks codex plugin add, use a plugin-capable
client or the direct MCP configuration below.
To use your own build, or to avoid the .NET 10 SDK requirement, register the
published executable directly instead of installing the plugin:
codex mcp add wpf-visual-tree -- "C:/Tools/WpfVisualTreeMcp/server/WpfVisualTreeMcp.Server.exe"
Replace the example with the actual executable path. Avoid enabling both this
manual entry and the plugin at the same time, which would start two servers.
Plugin files are under plugins/wpfvisualtreemcp/; the marketplace entry is
.agents/plugins/marketplace.json. The plugin uses Codex's supported
.codex-plugin/plugin.json compatibility format. Its manifest version identifies
the plugin configuration and skill, independently of the NuGet server version.
The MCP launch omits a package version and uses --no-http-cache to resolve the
latest stable release from nuget.org on each start. Prereleases are excluded.
Restart the MCP server or Codex to pick up a new server release; a running server
does not update in place. Never add CLI subcommands
such as list to the MCP launch arguments: no subcommand selects stdio mode.
The plugin starts in its own directory and includes a global.json selecting
SDK 10.0.300 or a newer stable .NET 10 SDK. This keeps a target project's older SDK pin
from disabling dotnet dnx. The noninteractive launch and x64/x86 Inspector
injection were verified with SDK 10.0.402 and Codex CLI 0.162.1. The SDK pin keeps
the launch on the tested .NET 10 command-line behavior.
The compatibility MCP configuration uses "cwd": ".", which Codex resolves
relative to the installed plugin root. This resolution was verified through
codex mcp list --json after installation in an isolated profile.
After editing local plugin files, rerun codex plugin add wpfvisualtreemcp@WPFVisualTreeMcp
to refresh the installed copy, then open a new Codex session.
For a Git-backed marketplace, update the plugin configuration and companion skill with:
codex plugin marketplace upgrade WPFVisualTreeMcp
codex plugin add wpfvisualtreemcp@WPFVisualTreeMcp
For a local marketplace, update its source checkout before reinstalling the plugin.
The companion skill covers mouse dragging, touch gestures and update behavior.
wpfinspect update updates a separately installed CLI or portable copy; it does
not refresh a plugin or its skill, and should not be used to modify the plugin's
shared dnx package cache. See Updating for standalone installations.
Self-Hosted Mode (Recommended)
For your WPF application to be inspectable, add a reference to the Inspector DLL and initialize it on startup:
-
Add a project reference to WpfVisualTreeMcp.Inspector
-
In your App.xaml.cs:
using System.Diagnostics;
using System.Windows;
using WpfVisualTreeMcp.Inspector;
public partial class App : Application
{
protected override void OnStartup(StartupEventArgs e)
{
base.OnStartup(e);
InspectorService.Initialize(Process.GetCurrentProcess().Id);
}
protected override void OnExit(ExitEventArgs e)
{
InspectorService.Instance?.Dispose();
base.OnExit(e);
}
}
This enables the MCP server to connect to your application via named pipes for real-time inspection.
Usage Examples
List Running WPF Applications
Use the wpf_list_processes tool to show all running WPF applications.
Attach and Inspect Visual Tree
Attach to the MyApp.exe WPF application and show me the visual tree of the main window.
Find Binding Errors
Check the attached WPF application for any binding errors and explain what's causing them.
Search for Elements
Find all Button elements in the visual tree that have IsEnabled set to false.
Export Visual Tree
Export the visual tree of the current window to JSON format so I can analyze the structure.
Architecture
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β AI Agent (Claude Code) β
βββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββββ
β MCP Protocol (stdio)
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β WpfVisualTreeMcp Server β
β βββββββββββββββββββ βββββββββββββββββββ βββββββββββββββ β
β β MCP Handler β β Tree Navigator β β Injector β β
β β (Tools/Res.) β β & Inspector β β Manager β β
β ββββββββββ¬βββββββββ ββββββββββ¬βββββββββ ββββββββ¬βββββββ β
βββββββββββββΌβββββββββββββββββββββΌββββββββββββββββββββΌβββββββββ
β β β
ββββββββββββββββββββββΌββββββββββββββββββββ
β Named Pipes / IPC
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Target WPF Application β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β Injected Inspector DLL ββ
β β β’ VisualTreeHelper access ββ
β β β’ LogicalTreeHelper access ββ
β β β’ Property/Binding inspection ββ
β β β’ Resource dictionary enumeration ββ
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
For detailed architecture documentation, see docs/ARCHITECTURE.md.
| Tool | Description |
|---|
wpf_list_processes | List all running WPF applications |
wpf_attach | Attach to a WPF application (supports auto_inject for DLL injection) |
wpf_get_visual_tree | Get the visual tree hierarchy (default depth: 25, max: 100) |
wpf_get_element_properties | Get all dependency properties of an element |
wpf_find_elements | Query elements by exact AutomationId, type, x:Name, visible text, property values and visibility; results include text, automation id, enabled/visible state and screen bounds |
wpf_find_elements_deep | Same query filters without result limit, across all windows including adorners/popups |
wpf_capture_screenshot | Capture a screenshot of the window or element (returns image); mode='screen' includes popups and menus; full_content=true with render mode captures scrollable content |
wpf_report | Aggregate current binding/validation errors, UI state counts and recent binding traces, with explicit scan limits and coverage |
wpf_record / wpf_get_recording | Start, stop, inspect or clear a workflow recording with stable selectors |
wpf_assert | Assert a dependency-property value; successful assertions are included in active recordings |
wpf_replay | Replay a workflow against a fresh app, stopping at the first failed step |
wpf_export_test | Export a stopped recording as a runnable xUnit project or workflow JSON |
wpf_get_bindings | Get data bindings for an element (includes MultiBinding, converter, StringFormat) |
wpf_get_binding_errors | List all captured binding errors |
wpf_clear_binding_errors | Clear the captured binding errors list |
wpf_get_data_context | Get DataContext type, properties, INPC status, and inheritance chain |
wpf_get_resources | Enumerate resource dictionaries |
wpf_get_styles | Get applied styles and templates |
wpf_watch_property | Monitor a property for changes |
wpf_evaluate_binding | Explain why a property has its value β value source, and for bindings a hop-by-hop path resolution pinpointing where a broken binding fails |
wpf_explain_triggers | Evaluate Style and ControlTemplate triggers against the current state (condition, current value, active, setters) β 'why doesn't this trigger fire?'; and attribute a property's value to the style setter / active trigger that set it |
wpf_snapshot | Capture an element subtree's state (layout, visibility, brushes, text) under a label |
wpf_diff | Diff two snapshots β measure exactly what a change moved (property fromβto, added/removed) |
wpf_set_property | Live-edit a dependency property at runtime (type-converted), to test a change without rebuilding. State-changing, reversible. |
wpf_revert_property | Undo wpf_set_property edits (one, filtered, or all) β restores the prior binding/value/default. |
wpf_highlight_element | Visually highlight an element |
wpf_click_element | Click a control by handle or AutomationId β pass automation_id="form.clear" directly; optional root_handle scopes lookup and duplicate IDs fail. UI Automation invoke by default, physical=true for a real OS mouse click, click_type='double'/'right' for double/right clicks. State-changing. |
wpf_move_mouse | Move/hover at a local point without clicking. Available from v0.17.0. |
wpf_scroll | Wheel input vertically or horizontally; the app decides whether to scroll or zoom. Available from v0.17.0. |
wpf_drag | Drag with the mouse β source and target elements or relative displacement, local points, left/right/middle button, gradual movement and release cleanup. State-changing. |
wpf_touch_gesture | Native touch β tap, long press, swipe, two-finger pinch and rotation inside a visible element. Requires application touch support. State-changing. |
wpf_select_item | Select an item in a ComboBox/ListBox/ListView/TabControl by visible text or index β works with virtualized items. State-changing. |
wpf_wait_for | Wait until an element is visible/exists/enabled/hidden, polling in the target app β no sleep-and-retry loops. |
wpf_set_text | Set text/value of a TextBox/ComboBox/PasswordBox β UI Automation IValueProvider.SetValue by default, physical=true to type via OS keyboard input. State-changing. |
wpf_send_keys | Send a keyboard shortcut (Ctrl+S, Alt+F4, F5, Enter, ...) to an element or the focused window. State-changing. |
wpf_get_layout_info | Get layout information |
wpf_export_tree | Export visual tree to XAML or JSON |
For complete tool documentation, see docs/TOOLS_REFERENCE.md.
All input actions accept automation_id instead of element_handle, including
click, mouse movement, scrolling, drag, every touch gesture, selection, text and
keyboard input. Assertions and property edits accept it too. IDs match
AutomationProperties.AutomationId exactly and case-sensitively; duplicates fail.
Use root_handle to scope lookup. Drag destinations accept target_automation_id
and an independent target_root_handle. The same selectors work in recordings
and exported tests.
wpf_touch_gesture(automation_id="Canvas", gesture="tap")
wpf_touch_gesture(automation_id="Canvas", gesture="swipe", delta_x=80)
wpf_touch_gesture(automation_id="Canvas", gesture="pinch", scale=1.5)
wpf_drag(automation_id="Source", target_automation_id="Destination")
wpf_set_text(automation_id="UserName", text="test")
wpf_assert(automation_id="UserName", property_name="Text", expected_value="test")
CLI equivalents use --automation-id, --root, --target-automation-id and
--target-root. Touch pan uses swipe, zoom uses pinch; the app must support
touch/manipulations to react to those gestures.
Roadmap
Phase 1: Core Inspection β
Phase 2: Advanced Features β
Phase 3: Interaction & Diagnostics β
Phase 4: CLI + Driving the App β
(v0.4.0 / v0.5.0)
Phase 5: Multi-architecture β
(v0.6.0)
Phase 6: Query engine & full driving β
(v0.7.0)
Phase 7: Distribution & agent ergonomics β
(v0.7.1 / v0.8.0)
Next up
Shipped in v0.13.0: mouse dragging and native touch gestures, with MCP/CLI parity,
sample demos, input cleanup, and real desktop validation across net48 x86/x64 and net8 x64.
Shipped in v0.14.0: CLI self-update with version checks and installation status.
Shipped in v0.15.0: Codex plugin marketplace, companion skill and plugin ZIP.
Shipped in v0.16.0: workflow recording/replay/xUnit export, aggregate diagnostics,
full-content screenshots and .NET Framework 4.7.2 compatibility.
The "change β measure β is it effective?" loop is complete: live-edit a property, then
diff a before/after snapshot to see exactly what moved.
See docs/ROADMAP.md for the full prioritized plan (rationale,
design notes, effort, and suggested sequencing).
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Development Setup
-
Clone the repository:
git clone https://github.com/faze79/WpfVisualTreeMcp.git
cd WpfVisualTreeMcp
-
Open in Visual Studio 2022 or VS Code:
code .
start WpfVisualTreeMcp.sln
-
Build and run tests:
-
Run the sample WPF app for testing:
dotnet run --project samples/SampleWpfApp
Project Structure
WpfVisualTreeMcp/
βββ src/
β βββ WpfVisualTreeMcp.Server/ # MCP Server (.NET 8) - Uses official MCP SDK
β β βββ Program.cs # Server initialization with MCP SDK
β β βββ WpfTools.cs # 38 inspection, interaction and workflow tools
β β βββ Cli/CliRunner.cs # One-shot CLI front-end (v0.4.0)
β β βββ Services/ # Process & IPC management
β βββ WpfVisualTreeMcp.Inspector/ # Injected DLL (Framework 4.7.2/4.8/4.8.1; .NET 8/9/10)
β βββ WpfVisualTreeMcp.Injector/ # Managed injection logic (CreateRemoteThread; net48 + net8.0)
β βββ WpfVisualTreeMcp.InjectorHelper/# x86 .NET 8 helper exe for cross-arch injection (v0.6.0)
β βββ WpfVisualTreeMcp.Bootstrapper/ # Native C++ DLL for CLR hosting
β βββ WpfVisualTreeMcp.Shared/ # Shared models & IPC contracts
βββ samples/
β βββ SampleWpfApp/ # Test application
βββ tests/
β βββ WpfVisualTreeMcp.Tests/ # Unit tests
β βββ WpfVisualTreeMcp.IntegrationTests/ # Live WPF integration tests
βββ publish/ # Published server + native DLLs
β βββ native/{x64,x86}/ # Architecture-specific bootstrapper
βββ docs/ # Documentation
Technical Details
- MCP SDK: Built with the official C# MCP SDK from Microsoft/Anthropic
- Protocol: JSON-RPC 2.0 over stdio transport
- Target Framework: .NET 8.0 (Server) / .NET Framework 4.7.2, 4.8 and .NET 8.0-windows (Inspector)
- IPC: Named Pipes for server-to-application communication
- Tools: 38 tools auto-discovered via
[McpServerTool] attributes, covering inspection, diagnostics, interaction and workflow recording/testing. Replay performs recorded actions; full-content screenshots may temporarily scroll controls.
- CLI: same executable runs as one-shot CLI when given a subcommand (
Program.cs routes via CliRunner.IsCliCommand)
Acknowledgments
License
This project is licensed under the MIT License - see the LICENSE file for details.