AutoMobile vs WPFVisualTreeMcp
A side-by-side look at the AutoMobile and WPFVisualTreeMcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AutoMobile for os automation work as a local process; choose WPFVisualTreeMcp for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AutoMobile when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose WPFVisualTreeMcp when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
- You want tools like
wpf_list_processes, wpf_attach, wpf_get_visual_tree.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 49/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 52 | 20 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 35 |
| Full listing | View AutoMobile | View WPFVisualTreeMcp |
Tools & capabilities
AutoMobile tools
No tool names declared yet. Check the project README from the listing page.
WPFVisualTreeMcp tools 35
wpf_list_processesList all running WPF applicationswpf_attachAttach to a WPF application (supports `auto_inject` for DLL injection)wpf_get_visual_treeGet the visual tree hierarchy (default depth: 25, max: 100)wpf_get_element_propertiesGet all dependency properties of an elementwpf_find_elementsQuery elements by type, x:Name, **visible text**, property values and visibility; results include text, automation id, enabled/visible state and screen boundswpf_find_elements_deepSame query filters without result limit, across all windows including adorners/popupswpf_capture_screenshotCapture a screenshot of the window or element (returns image); `mode='screen'` includes popups and menus; `full_content=true` with render mode captures scrollable contentwpf_reportAggregate current binding/validation errors, UI state counts and recent binding traces, with explicit scan limits and coveragewpf_recordStart, stop, inspect or clear a workflow recording with stable selectorswpf_assertAssert a dependency-property value; successful assertions are included in active recordingswpf_replayReplay a workflow against a fresh app, stopping at the first failed stepwpf_export_testExport a stopped recording as a runnable xUnit project or workflow JSON- +23 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AutoMobile
{
"mcpServers": {
"automobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile"
]
}
}
}
WPFVisualTreeMcp
No confirmed install command for WPFVisualTreeMcp yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
AutoMobile is categorized under OS Automation and uses a local stdio subprocess. WPFVisualTreeMcp belongs to OS Automation and uses an install path we have not confirmed yet. Pick AutoMobile for os automation work and WPFVisualTreeMcp for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. WPFVisualTreeMcp has no confirmed install command yet — follow its own setup instructions.
AutoMobile is listed as free. Auth: no auth required. WPFVisualTreeMcp is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add automobile and faze79-wpfvisualtreemcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AutoMobile has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 52 GitHub stars. WPFVisualTreeMcp has 56/100 (Good) with 4 views, 0 installs and 20 GitHub stars.