winuse-mcp

Computer use for Claude Code on Windows. An MCP server that lets Claude see your screen and drive your mouse and keyboard.

Claude Code ships computer use in the CLI on macOS only, so on Windows the computer-use server never appears in /mcp. This rebuilds the same screenshot-and-click loop on the Windows APIs: 14 tools, 5 dependencies, Python 3.12.

Install

Needs Windows and uv. Add this to .mcp.json in a project, or to ~/.claude.json for every project:

{
  "mcpServers": {
    "winuse": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/ryanportfolio/winuse-mcp", "winuse-mcp"]
    }
  }
}

From a local clone instead:

{
  "mcpServers": {
    "winuse": {
      "command": "uv",
      "args": ["run", "--directory", "C:/path/to/winuse-mcp", "winuse-mcp"]
    }
  }
}

Restart Claude Code, then ask it to look at your screen or click through an app.

Related MCP server: Win:Computer Use

Reach

Coordinates are always in screenshot space. See below.

How coordinates work

Screenshots are downscaled so the long edge is at most 1372 pixels, the same target Claude Code uses on macOS. Claude never sees native pixels, so it clicks in the downscaled image and the server converts back.

A 1920x1080 display captures at 1372x772, a factor of 0.715. A click at 686, 443 lands at 960, 620.

The server declares itself DPI-aware at startup, so Windows display scaling at 125% or 150% does not skew where clicks land.

Safety

This hands a language model control of your desktop. Anthropic's own version wraps the same loop in guardrails this server does not have: per-app approval, hiding apps Claude has not been approved for, keeping your terminal out of the screenshots, and model-side checks on each action.

What you do get:

• Claude Code asks before each tool call unless you allow-list it. Keep the input tools on manual approval and only allow-list screenshot.

• Park the mouse in the top-left corner of the screen to abort the action in flight. That is pyautogui's failsafe, and it only watches that one corner. Aborting mid-drag releases the mouse button on the way out, so nothing is left dragging.

• Everything visible reaches the model, including whatever happens to be on screen. Text on screen is untrusted input: treat instructions that appear there as a prompt injection risk.

Limitations

• Primary monitor only.

• Your terminal is not excluded from screenshots, so Claude sees its own session.

• record samples still frames, at most 8 of them. There is no video path.

Development

uv sync
uv run winuse-mcp

scripts/client_test.py is the reference check: it speaks MCP over stdio to the server, lists the tools, takes a screenshot, moves the mouse and reads the position back, records frames, and asserts a bad key combo errors.

uv run python scripts/client_test.py

scripts/failsafe_test.py covers the paths a user hits while aborting, with pyautogui stubbed so no real abort is needed: a drag cut short still releases the button, a horizontal scroll cut short still releases shift, chord parsing handles a literal +, and no click can land on the failsafe pixel.

uv run python scripts/failsafe_test.py

This README is built. Every number on the page is recomputed from the source at build time, and the build fails if one drifts.

node scripts/readme/build.mjs

License

MIT