# Windows-MCP [Health: Active]

**Category:** 🖥️ OS Automation  
**Repository:** https://github.com/CursorTouch/Windows-MCP  
**GitHub Stars:** 11412  
**Views:** 22  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/windows-mcp

## Description
An MCP Server for computer-use in Windows OS

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "windows-mcp": {
    "command": "uvx",
    "args": ["windows-mcp"]
  }
}
```

## Documentation

## What Windows-MCP does

Windows-MCP gives MCP-compatible AI agents access to Windows desktop interaction. It is intended for automation tasks that require more than API calls, including navigating files, launching applications, controlling windows, simulating keyboard and mouse input, inspecting UI state, and performing QA workflows.

The server targets Windows 10 and Windows 11. Its interaction model works with any LLM and does not require traditional computer-vision methods or a dedicated fine-tuned model. Vision can be used by the connected model when appropriate, but it is not presented as a server requirement.

## How it works

The server runs locally on the Windows machine and exposes its automation operations through the Model Context Protocol. It can run directly with `uvx windows-mcp serve`, or be configured as a background task that starts at login. Supported transports include the default local stdio mode, Server-Sent Events, and streamable HTTP.

Actions generally take between 0.2 and 0.5 seconds from one interaction to the next. Actual timing varies with system load, the number of open applications, and the connected model's inference speed.

Browser automation has a DOM mode enabled with `use_dom=True` on the State tool. This mode concentrates on webpage content instead of browser chrome and is available for Chrome, Edge, and Firefox. Firefox uses an IAccessible2 fallback because it does not expose `RootWebArea` through UI Automation.

## Setup and configuration

Install Python 3.14 or newer and the uv package manager. The PyPI package can be launched with:

```shell
uvx windows-mcp serve
```

For network transports, specify the transport, host, and port, such as `--transport sse --host localhost --port 8000` or `--transport streamable-http --host localhost --port 8000`.

The `windows-mcp install` command creates a per-user Windows Scheduled Task named `windows-mcp-server`, starts it immediately, and runs it at future logins. The wrapper script is stored at `~/.windows-mcp/start-server.cmd`; logs are written to `~/.windows-mcp/server.log` and `server.error.log`. Run `windows-mcp uninstall` to remove the task.

Claude Desktop can use a stdio configuration that invokes `uvx windows-mcp serve`. The Microsoft Store edition requires extra care: its MSIX sandbox uses a different configuration path and may require an absolute path to `uvx.exe`, `uv.exe`, or the installed `windows-mcp.exe`.

## Tools and capabilities

- Open applications and resolve localized Start Menu display names.
- Navigate files and interact with Windows UI elements.
- Send basic keyboard and mouse input.
- Control windows and capture current UI state.
- Use DOM-focused state inspection for supported browsers.
- Adapt or extend the available tools for custom automation needs.

## Limitations and notes

The current package requires Python 3.14 or later and supports Windows 10 and newer. Earlier Windows versions are not supported. The first installation may take one or two minutes while dependencies are installed, and the initial server run may time out; restarting it is recommended. The server is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/windows-mcp/readme_