Windows MCP
Let Claude Code, Cursor, or other MCP clients drive real Windows desktop actions—apps, UI, and workflows—without you clicking through every step.
Overview
io.github.CursorTouch/Windows-MCP is an MCP server for the Build phase that enables AI agents to perform computer-use tasks on Windows through stdio MCP and the windows-mcp PyPI package.
What is this MCP server?
- MCP stdio server aimed at computer-use on Windows (not browser-only automation)
- PyPI package windows-mcp (0.8.1) with runtimeHint uvx for quick local runs
- Published server schema 2025-07-09; catalog entry version 1.0.1
- Open-source repo CursorTouch/Windows-MCP on GitHub
- Fits solo builders who ship on Windows and want agents to operate native apps and the shell
- Catalog server version 1.0.1; PyPI package windows-mcp version 0.8.1
- Single stdio transport package in server.json
- runtimeHint uvx; registryType pypi; identifier windows-mcp
Community signal: 5.9k GitHub stars.
What problem does it solve?
Your agent can write code but cannot reliably operate Windows apps and the desktop UI, so you keep context-switching to click through native workflows yourself.
Who is it for?
Solo builders on Windows who want MCP-backed desktop automation while building agent-assisted products or internal tools.
Skip if: Teams on macOS/Linux-only stacks, or anyone who refuses to grant an agent desktop control on their primary Windows machine.
What do I get? / Deliverables
After you register the server with uvx and your MCP client, the agent can drive Windows computer-use from the same session instead of you manually executing every desktop step.
- Registered stdio MCP server entry wired to windows-mcp via uvx
- Agent-callable Windows computer-use tools from your coding session
- Repeatable local desktop automation without custom Win32 scripts per task
Recommended MCP Servers
Journey fit
Desktop computer-use is agent infrastructure you wire up while building your stack, not a launch or growth tactic. The server exposes Windows OS control to agents via MCP stdio, which is classic agent-tooling alongside other MCP bridges.
How it compares
Windows desktop MCP integration, not a reusable Claude skill markdown workflow.
Common Questions / FAQ
Who is io.github.CursorTouch/Windows-MCP for?
It is for indie and solo developers on Windows who use MCP clients such as Cursor or Claude Code and want the agent to perform computer-use on the OS, not only edit files.
When should I use io.github.CursorTouch/Windows-MCP?
Use it during Build when you are adding agent-tooling and your workflow depends on native Windows UI, legacy apps, or shell-level actions that APIs do not cover.
How do I add io.github.CursorTouch/Windows-MCP to my agent?
Install the PyPI package windows-mcp (0.8.1), run it via uvx with stdio transport, and add the server entry to your MCP client configuration pointing at that command.