Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Automate Windows WPF apps from AI agents with semantic UIA selectors and FlaUI test generation.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"wpfpilot": {
"command": "npx",
"args": [
"-y",
"@skuzadev/wpfpilot-mcp"
]
}
}
}Run this in your terminal
claude mcp add wpfpilot -- npx -y @skuzadev/wpfpilot-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wpfpilot": {
"command": "npx",
"args": [
"-y",
"@skuzadev/wpfpilot-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"wpfpilot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@skuzadev/wpfpilot-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account skuzadev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
WpfPilot MCP is a local Model Context Protocol server for Windows WPF applications. It lets AI coding agents inspect UI Automation trees, click and type through semantic selectors, diagnose WPF-specific issues, record workflows, and generate xUnit + FlaUI tests.
npx (recommended). No .NET SDK required for the release binary or npm launcher.Add this to your MCP client configuration (global or project-scoped):
{
"mcpServers": { "wpfpilot-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@skuzadev/wpfpilot-mcp"] } } }
Or run directly (stdio; waits for an MCP client):
npx -y @skuzadev/wpfpilot-mcp
The npm launcher downloads the latest Windows release binary on first run, then proxies stdio to it.
Other installs (persistent wpfpilot-mcp command, release zip, uninstall): see Install WpfPilot.
Use the standard config above unless noted. More clients: docs/all-clients.md.
Cursor
Global: ~/.cursor/mcp.json (do not add a project .cursor/mcp.json unless you need a repo-specific override)
{
"mcpServers": { "wpfpilot-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@skuzadev/wpfpilot-mcp"] } } }
Or: Cursor Settings → MCP → Add new MCP Server — command npx, args -y @skuzadev/wpfpilot-mcp.
cursor-agent mcp list
cursor-agent mcp list-tools wpfpilot-mcp
Codex
codex mcp add wpfpilot-mcp -- npx -y @skuzadev/wpfpilot-mcp
codex mcp list
Or ~/.codex/config.toml:
[mcp_servers.wpfpilot-mcp]
command = "npx" args = ["-y", "@skuzadev/wpfpilot-mcp"] enabled = true startup_timeout_sec = 30 tool_timeout_sec = 60
Claude Code
claude mcp add --transport stdio wpfpilot-mcp -- npx -y @skuzadev/wpfpilot-mcp
claude mcp list
Project .mcp.json:
{
"mcpServers": { "wpfpilot-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@skuzadev/wpfpilot-mcp"] } } }
Claude Desktop
Windows config: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": { "wpfpilot-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@skuzadev/wpfpilot-mcp"] } } }
Restart Claude Desktop after saving.
VS Code
Create .vscode/mcp.json:
{
"servers": { "wpfpilot-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@skuzadev/wpfpilot-mcp"] } } }
Or: code --add-mcp '{"name":"wpfpilot-mcp","command":"npx","args":["-y","@skuzadev/wpfpilot-mcp"]}'
After connecting the MCP client, ask:
List the WpfPilot tools and attach to my running WPF application.
Useful follow-up prompts:
Show the main window UI tree.
Click the Save button using a selector, not coordinates. Wait until the status text says Saved. Why is the Submit button disabled? Record this workflow and generate an xUnit test.
| Tool | Purpose |
|---|---|
wpf_capabilities | List supported verbs, query kinds, and wait conditions. |
wpf_query | Read UI state. |
wpf_act | Perform UI actions. |
wpf_wait | Wait for UI state. |
wpf_assert | Verify UI state. |
Full tool list: docs/tools-reference.md.
The probe runs inside your WPF process and exposes diagnostics that UI Automation cannot see directly (bindings, ViewModels, commands, validation).
Use wpf_probe_connect, then inspect my ViewModel and binding errors.
Setup: docs/probe-setup.md.
WpfPilot is intended for local development and test automation.
wpfpilot-mcp is not recognized
Restart your terminal after running the installer, or use the full path to wpfpilot-mcp.exe in your MCP client configuration. See all-clients.md.
Server starts but no tools appear
Restart the MCP client and check its MCP logs. Also verify npx -y @skuzadev/wpfpilot-mcp runs from a normal terminal.
Cannot attach to an app
Make sure the WPF app is running in the same user session and at a compatible privilege level. If the app runs as administrator, the MCP client may also need to run elevated.
Probe cannot connect
Confirm the target app called ProbeHost.Start(), then use wpf_probe_status and wpf_probe_connect. If needed, pass wpfpilot-mcp-probe-{ProcessId} explicitly.
See CONTRIBUTING.md.
MIT. See LICENSE.