Server facts
Windows-MCP
Project
- Author
- CursorTouch
- Repository
- github.com/CursorTouch/Windows-MCP
- License
- MIT
- Category
- Mobile & Desktop Automation
Tech
- Runtime / language
- pythonPython
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 9,410
- Last commit
- Data as of
Tags
- Browser Dom
- Desktop Automation
- Ui Testing
- Windows
Overview
Windows-MCP connects AI assistants to native Windows desktop interaction. The README describes opening applications, navigating files, controlling windows, simulating input, and inspecting UI state for automation or QA work. It is designed to work with different LLMs without requiring a dedicated vision model. Browser-focused DOM mode narrows state inspection to page content rather than the surrounding browser interface, with Chrome, Edge, and Firefox support described. The supported operating-system list spans Windows 7 through Windows 11.
Local setup uses the Python package through uvx and requires Python 3.13 or newer. English is preferred for Windows application control; otherwise the README advises disabling the application tool. Stdio is the default, while SSE and Streamable HTTP support network clients. A scheduled-task installation can start the service at login, and documentation covers several desktop and command-line assistants. Remote deployment brings additional controls: bearer authentication, IP allowlists, TLS, explicit CORS origins, and OAuth with PKCE are documented. Tools are all enabled initially, but command-line selection can allow only chosen tools or exclude capabilities such as PowerShell and Registry. WSL clients must still launch the server on the Windows side because it relies on Windows APIs. Initial dependency installation and packaged desktop-client path handling can also require troubleshooting before the connection is usable.
Install & configure
Requirements
- Windows
- Python 3.13+
- uv with uvx
- An MCP-compatible client
uvx windows-mcp serveThis is the documented default stdio launch. English is preferred for App-Tool; disable that tool for other Windows languages. For network access, configure authentication and TLS rather than using an unprotected listener.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"Windows-MCP": {
"command": "uvx",
"args": [
"windows-mcp",
"serve"
],
"env": {}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"Windows-MCP": {
"command": "uvx",
"args": [
"windows-mcp",
"serve"
],
"env": {}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"Windows-MCP": {
"type": "stdio",
"command": "uvx",
"args": [
"windows-mcp",
"serve"
],
"env": {}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"Windows-MCP": {
"command": "uvx",
"args": [
"windows-mcp",
"serve"
],
"env": {}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"Windows-MCP": {
"type": "stdio",
"command": "uvx",
"args": [
"windows-mcp",
"serve"
],
"env": {}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| Screenshot | Capture screen imagery; this tool name appears in the README's tool-selection example. |
| Click | Perform a mouse click; this tool name appears in the README's tool-selection example. |
| Snapshot | Inspect desktop state; this tool name appears in the README's tool-selection example. |
| PowerShell | Expose PowerShell capability, which the README demonstrates excluding from the enabled tool set. |
| Registry | Expose Windows Registry capability, which the README demonstrates excluding from the enabled tool set. |
Use cases
- Automate application and window interactions on a Windows desktop.
- Perform UI-driven QA tasks through an assistant.
- Inspect web page content using the browser DOM mode.
- Expose selected desktop tools to a secured network client.
Strengths
- Works with different LLMs without requiring a specialized vision model.
- Supports local stdio plus SSE and Streamable HTTP.
- Documents authentication, TLS, IP filtering, and tool selection.
Limitations
- Requires Windows-side execution even when the assistant runs in WSL.
- Python 3.13+ is required by the documented setup.
- Non-English Windows setups may need the application tool disabled.
Windows-MCP setup notes
- Windows-MCP's stdio example needs a client that launches local processes.