Netwright runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Nov 2026.
Playwright-style automation of .NET desktop apps (WPF, WinForms, WinUI) for AI agents.
What the code does
We read the source, 22 h ago · rules 995398eba69f
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 startInfo = new ProcessStartInfo(dotnet, arguments.ToString())
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 Netwright
same job, measured the same wayPlaywright for the Windows desktop, from Bun — drive native GUIs via UI Automation + MCP.
Background Windows desktop for AI agents: native GUI automation, screenshots and app testing.
Open automation engine for AI agents. Control live browsers and desktop apps locally.
Desktop and mobile website screenshots plus page context for AI agents and automation workflows.
MCP server for AI agents to interact with terminal applications. Think Playwright for terminals.
MCP server for Fetch Pet insurance claims management using Playwright automation.
Playwright & Appium test automation for Claude. Generate tests, diagnose failures, open fix PRs.
MCP server for browser automation with AI agent
Netwright — questions
Answers built from our own checks of this server.