XamlMcp runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 5 Aug 2026.
Inspect and drive Avalonia, WPF, WinUI, and .NET MAUI apps through MCP.
What the code does
We read the source, 1 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
var start = new ProcessStartInfo(request.FileName)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to XamlMcp
same job, measured the same wayNotes, files, GitHub, and Drive through one MCP connection.
Notes, files, GitHub, and Drive through one MCP connection.
Let AI agents inspect and drive running WPF apps: tree, bindings, screenshots, clicks, text input.
Notes, files, GitHub, and Drive through one MCP connection.
Drive a Tailscale node and its tailnet through the CLI and the control-plane API
Inspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments.
Let AI drive Swing and JavaFX apps — see the UI, click, fill forms, read tables. No API needed.
Inspect and drive Flutter debug apps/games: semantic snapshots, search, and custom client tools
XamlMcp — questions
Answers built from our own checks of this server.