NexusWindows runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
We read the source, 10 min 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.
const child = spawn(helper, ['--mcp', '--agent', agent], { stdio: 'inherit', windowsHide: true });
const cache = path.join(home, 'plugins', 'cache', 'nexus-plugins', 'nexus-windows', manifest.version);
var start = new ProcessStartInfo(Program.HelperExecutable is { Length: > 0 } helper ? helper : throw new InvalidOperationException("Helper path unavailable"), "--com-worker")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
Lets Claude drive your REAL mouse, keyboard and screen - works in your own logged-in apps.
Sandboxed computer-use for AI agents: drive real browser + desktop apps in nested X11 windows
Focus-free macOS control for AI agents: drive your real Mac apps in the background, no stolen focus.
Computer-use for Kasm Workspaces: lets AI agents see and drive your Kasm desktops over KasmVNC.
Your Kubernetes clusters for AI agents through the KubeDrive desktop app, without a kubeconfig.
Playwright for the Windows desktop, from Bun — drive native GUIs via UI Automation + MCP.
Drive AirSCP, the Mac app for SCP/SFTP file transfers, SSH servers and Windows Remote Desktop
Let agents drive Revit, AutoCAD, SketchUp, Blender and PDF sets on your own Windows desktop.
Answers built from our own checks of this server.