Windows-MCP
MCP Server for Computer Use in Windows
Runssource: GitHubPythonMITcommit 1ea8690a6d9b
Python, MIT licensed. The project labels itself: ai, desktop, mcp, tools, windows and windows automation.
Windows-MCP runs. An Argusic agent installed it in 2 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
285 tests passing, 321 skipped (Windows-only); CLI entry point responds to --help; MCP server with stdio/SSE/streamable-http transport available.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 21 test files import Windows-only modules at module level3 minutes
- pywin32, comtypes, dxcam have no Linux wheels; uv sync fails2 minutes
- uia/enums.py calls os.sys.getwindowsversion() and ctypes.windll at module level on Linux2 minutes
- uia/__init__.py unconditionally imports core/patterns/controls/events that need comtypes2 minutes
- uia/exceptions.py imports _ctypes.COMError (Windows-only)1 minute
- desktop/utils.py imports pywintypes at module level1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 64 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- uv run pytest -q --tb=no on the 14 cross-platform test files (analytics, check_versions, cli_legacy_flags, cli_paired_flags, config_stateless, config_validation, desktop_utils, desktop_views, filesystem_views, no_stdout_writes, paths, startup_dependency_guard, surrogate_repair, tree_budget, tree_views): 228 passed, 1 skipped. uv run windows-mcp --help prints the CLI group with serve/install/uninstall/auth subcommands.
- Model tokens used
- 1,130,495
- Exact commit tested
- 1ea8690a6d9b
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Now I'll produce the final structured report. `uv sync` succeeds with the platform-marker fix, `uv run windows-mcp --help` prints the CLI group h… **Errors encountered and fixed:** - **pywin32/comtypes/dxcam: no Linux wheels** — added `; sys_platform == 'win32'` markers to `pypro… - **`os.sys.getwindowsversion()` in uia `enums.py`, `core.py`, `controls.py`, `patterns.py`** — gua… - **`ctypes.windll` in `uia/enums.py`** — guarded `RegisterClipboardFormatW` with `hasattr(ctypes, … - **`from _ctypes import COMError` in `uia/exceptions.py`** — conditionally imported - **`import pywintypes` in `desktop/utils.py`** — moved inside the only function that needs it - **`vdm/__init__.py` unconditionally imported `comtypes`** — guarded with sys.platform; provided L… - **`desktop/service.py` imported from `vdm.core`** — changed to `vdm` so the `__init__.py` guard a… - **`powershell/service.py: import winreg`** — guarded with a Linux stub class - **21 test files unconditionally imported Windows-only modules** — added `pytestmark` skip markers
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes, faster than the median of the 36 comparable projects Argusic has measured.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 37 ai projects Argusic has installed and timed, Windows-MCP was the 5th fastest to reach a running state, and 30 of 37 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.47 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.96 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/windows-mcp)Questions
- Does Windows-MCP run?
- Yes. Windows-MCP runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test Windows-MCP?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1ea8690a6d9b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Windows-MCP?
- The run that produced this verdict cost $0.96: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Windows-MCP take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Windows-MCP need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Windows-MCP?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Windows-MCP compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, Windows-MCP was the 5th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for Windows-MCP?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.