# Windows-MCP

> MIT MCP server that lets an agent drive the Windows desktop — apps, UI, input, shell

**Category:** AI Agents  
**Pricing:** open-source  
**URL:** https://github.com/CursorTouch/Windows-MCP  
**GitHub:** https://github.com/CursorTouch/Windows-MCP  
**Added:** 2026-10-09

---

## The Hook

Windows-MCP hands an MCP client the Windows desktop: launch and switch apps, read the UI tree, click, type, scroll, and run shell commands — computer use on Windows without a vision-only screenshot loop.

## What's Good

MIT (CursorTouch/Windows-MCP), release v0.8.7, on PyPI. `uvx windows-mcp serve` runs it over stdio; `--transport sse` or `--transport streamable-http` expose it on a local port. Works with Claude Desktop, Cursor, and any MCP client. Uses the accessibility tree, so it works with whatever model you already use. ★~8.4k.

## The Catch

Windows only (7 through 11). It drives your real desktop session with full system access — it is not a sandbox, so run it on a machine or VM you are happy to let an agent control, and keep secrets out of reach. The first install can take a minute or two while dependencies resolve, and the very first start may time out once. Vs cua (sandboxed computer-use VMs and SDK) and agent-desktop (desktop automation agent): Windows-MCP is the plain MCP server on the Windows host itself.

## Verdict

MIT Windows computer-use MCP when an agent must operate real Windows apps — run it on a disposable machine, never on a desktop you cannot afford to hand over.