Moonlight Desktop MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Oct 2026.
Visual Windows desktop control over Moonlight/GameStream for MCP clients and coding agents
What the code does
We read the source, 1 d 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(this.bridgePath, [], { stdio: ["pipe", "pipe", "pipe"] });
const directory = path.join(this.rootDirectory, id);
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 Moonlight Desktop MCP
same job, measured the same wayVisual Desktop Bridge - Give any AI full control over Windows to automate apps and inputs.
Control this Windows desktop from any MCP client: files, windows, keyboard and mouse.
Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
Verified desktop control for agents on Windows and Linux: apps with no API, windows, shell, browser.
Control Windows desktop via MCP: mouse, keyboard, screenshots, clipboard, and apps.
Real Linux and Windows desktop VMs for AI agents: exec, files, computer-use and snapshots via MCP.
Cited local coding-agent history for fresh Codex and Claude Desktop chats on Windows.
Local-first persistent memory for coding agents and MCP clients.
Moonlight Desktop MCP — questions
Answers built from our own checks of this server.