Windows-MCP

Use it when

• An AI agent needs to open, click, and type into native Windows applications that have no API or CLI.
• You want an MCP client like Claude Desktop to capture Windows UI state and automate multi-step desktop workflows such as QA testing or file navigation.

What it solves

Not the fit when

• Unsupervised use with PowerShell, Registry, filesystem, clipboard, or destructive UI actions enabled
• Network exposure without authentication, TLS, IP restriction, explicit origin policy, and a minimal tool allowlist
• Playing video games
• Non-Windows platforms
• Selecting exact text spans inside paragraphs
• Reliably typing source code into an IDE, which the README lists as a limitation
• cross-browser web scraping at scale
• macOS or Linux desktop control
• mobile app automation
• fine-grained text selection inside paragraphs
• typing code into an IDE reliably

Install

uvx windows-mcp serve (or: claude mcp add --transport stdio windows-mcp -- uvx windows-mcp serve)

Invoke

Register the local stdio server, then enable only the tools required for a supervised workflow, for example `--tools "Screenshot,Click,Snapshot"` or `--exclude-tools "PowerShell,Registry"`. Keep network transports on localhost unless authentication, TLS, an IP allowlist, and an explicit CORS allowlist are configured.

Alternatives

No reviewed alternatives recorded yet.