WpfBuddy MCP Server

The MCP server that understands WPF applications — not just pixels.

---

Attach to any WPF app. Inspect its UI tree semantically. Automate workflows without coordinates. Generate tests. Diagnose binding errors. All through natural language via MCP.

Why This Exists

Generic Windows automation tools can click and type. This server understands WPF.

Core Differentiator

Given any WPF screen, inspect it semantically, automate a workflow without raw coordinates, explain WPF-specific failures, record the workflow, replay it deterministically, and export a maintainable automated test.

Quick Start

Prerequisites

• .NET 8 SDK
• Windows 10/11 (UI Automation is Windows-only)

Build & Run

dotnet build WpfBuddyMcp.sln
dotnet run --project src/WpfBuddy.Mcp.Server

Connect Your MCP Client

{
  "mcpServers": {
    "wpfbuddy-mcp": {
      "command": "dotnet",
      "args": ["run", "--project", "src/WpfBuddy.Mcp.Server/WpfBuddy.Mcp.Server.csproj"]
    }
  }
}

{
  "mcpServers": {
    "wpfbuddy-mcp": {
      "command": "dotnet",
      "args": ["run", "--project", "C:/path/to/src/WpfBuddy.Mcp.Server/WpfBuddy.Mcp.Server.csproj"]
    }
  }
}

What Can It Do?

Attach & Inspect

"Attach to WPFapp and show me the main window structure"

The server attaches to any running WPF process, captures the full automation tree, and returns a semantic representation — control types, AutomationIds, names, patterns, states.

Automate Without Coordinates

"Click 'New Project', fill in Name as 'Test Project', then click Save"

All actions use semantic selectors (AutomationId → Name → ControlType), never raw screen coordinates. Selectors self-heal when the UI changes.

Record & Generate Tests

"Record what I'm doing, then export it as an xUnit test"

Records UI interactions as a workflow, validates selector stability, and exports production-ready xUnit + FlaUI test code with Page Object classes.

Diagnose WPF Issues

"Why is the Submit button disabled?"

With the optional in-process probe, inspects ViewModel command state, binding errors, DataContext properties, and validation — answering the "why" that generic tools cannot.

Accessibility Audit

"Run an accessibility check on this window"

Checks for missing names, keyboard accessibility, tab order, control patterns, and generates a report with recommendations.

Tool Categories

Full tool reference: docs/tools-reference.md

Architecture

┌─────────────────────────────────────────────────────────┐
│  MCP Client (VS Code Copilot, Claude Code, etc.)        │
└─────────────────────┬───────────────────────────────────┘
                      │ stdio (JSON-RPC)
┌─────────────────────▼───────────────────────────────────┐
│  WpfBuddy.Mcp.Server  (.NET 8)                          │
│                                                         │
│  ┌───────────────┐  ┌────────────┐  ┌─────────────────┐ │
│  │ SessionManager│  │ UiaAdapter │  │ SelectorBuilder │ |
│  │(attach/detach)│  │(FlaUI UIA3)│  │(heal/rank/build)│ |
│  └───────────────┘  └────────────┘  └─────────────────┘ │
│  ┌─────────────┐  ┌────────────┐  ┌─────────────────┐   │
│  │ Recording   │  │ Screenshot │  │   AuditLog      │   │
│  │  Service    │  │  Service   │  │                 │   │
│  └─────────────┘  └────────────┘  └─────────────────┘   │
│  ┌─────────────────────────────────────┐                │
│  │         ProbeClient (IPC)           │                │
│  └───────────────┬─────────────────────┘                │
└──────────────────┼──────────────────────────────────────┘
                   │ Named Pipe
┌──────────────────▼──────────────────────────────────────┐
│  Target WPF Application                                 │
│  ┌─────────────────────────────────────┐                │
│  │  WpfBuddy.Mcp.Probe (NuGet)         │                │
│  │  • ViewModel inspection             │                │
│  │  • Binding error capture            │                │
│  │  • Command state                    │                │
│  │  • Validation errors                │                │
│  │  • Dispatcher status                │                │
│  └─────────────────────────────────────┘                │
└─────────────────────────────────────────────────────────┘

Project Structure

wpf-buddy-mcp/
├── WpfBuddyMcp.sln
├── src/
│   ├── WpfBuddy.Mcp.Server/       # MCP server (main project)
│   │   ├── Program.cs                # Entry point, DI registration
│   │   ├── Services/                 # Core services
│   │   │   ├── SessionManager.cs     # Process attach/detach
│   │   │   ├── UiaAdapter.cs         # FlaUI wrapper
│   │   │   ├── SelectorBuilder.cs    # Selector generation & healing
│   │   │   ├── RecordingService.cs   # Workflow recording
│   │   │   ├── ScreenshotService.cs  # Screen capture
│   │   │   ├── ProbeClient.cs        # Named pipe IPC client
│   │   │   └── AuditLog.cs           # Action audit trail
│   │   ├── Tools/                    # MCP tool implementations
│   │   │   ├── SessionTools.cs
│   │   │   ├── SnapshotTools.cs
│   │   │   ├── ActionTools.cs
│   │   │   ├── WaitTools.cs
│   │   │   ├── AssertionTools.cs
│   │   │   ├── SelectorTools.cs
│   │   │   ├── DataGridTools.cs
│   │   │   ├── RecordingTools.cs
│   │   │   ├── TestGenerationTools.cs
│   │   │   ├── ScreenshotTools.cs
│   │   │   ├── AccessibilityTools.cs
│   │   │   ├── PolicyTools.cs
│   │   │   ├── ReportingTools.cs
│   │   │   ├── ClipboardTools.cs
│   │   │   ├── DiagnosticsTools.cs
│   │   │   ├── ProbeTools.cs
│   │   │   └── MvvmTools.cs
│   │   └── Models/                   # Data models
│   └── WpfBuddy.Mcp.Probe/        # In-process probe (NuGet package)
│       ├── ProbeHost.cs              # Named pipe server + WPF inspection
│       └── WpfBuddy.Mcp.Probe.csproj
└── docs/                             # Documentation

Safety & Security

Optional: In-Process Probe

For deep WPF diagnostics (bindings, ViewModel, commands), install the probe NuGet in your target app:

dotnet add package WpfBuddy.Mcp.Probe

// In App.xaml.cs
protected override void OnStartup(StartupEventArgs e)
{
    base.OnStartup(e);
    ProbeHost.Start();  // Listens on named pipe automatically
}

Then from MCP: wpf_probe_connect → full MVVM diagnostics available.

Probe setup guide: docs/probe-setup.md

Tech Stack

Documentation

Contributing

1. Fork & clone
2. dotnet build WpfBuddyMcp.sln
3. Make changes
4. Ensure build passes: dotnet build
5. Submit PR

License

MIT