dsh-windows-mcp: Windows Desktop Control for DeepSeek Harness

What Does It Do?

It is a DSH plugin for DeepSeek Harness that brings Windows desktop automation to the harness, letting the DSH agent see your screen and drive your PC. It connects CursorTouch/Windows-MCP to DSH by mounting a loader row against the MCP client bridge that already ships inside DeepSeek Harness, so there is no reimplemented protocol client and no second copy of the MCP SDK. Maintained by helloHub1212 under the MIT license and written in JavaScript, it was last updated on 2026-10-11.

Core Features

• Desktop tool set: once installed and reachable, the tool list gains mcp__windows__* tools for screenshots, accessibility-tree snapshots, display enumeration, mouse click/move/scroll, keyboard input and shortcuts, wait and wait-for conditions, window text scraping, clipboard access, process control, notification reading, and registry read/write.
• Computer Use pill: a pill next to the permission control shows how many desktop tools are actually registered and remembers your choice across restarts, with state kept in a dsh-windows-mcp.state.json file under your user directory.
• Off-by-default hard switch: a fresh install never hands the agent your desktop; when switched off the bridge keeps running, but from the next step every desktop tool is filtered out of the tool list the model sees and any call naming one is refused at dispatch, live across every session and subagent with no restart.
• Built-in diagnostics: the windows_mcp_doctor tool explains what is wrong when the mcp__windows__* tools are missing and always reports which way the switch is set.
• Default exclusions: the App launch/switch tool is excluded by default because upstream only supports it reliably on an English Windows install, and PowerShell and FileSystem are excluded too since DSH already ships shell and file tools.

How to Use This Plugin?

After enabling the plugin in DSH and making Windows-MCP reachable, the desktop tools appear in the tool list and you can simply ask the agent to take a screenshot, click, or type. A few prerequisites apply: Windows 10/11, DeepSeek Harness Desktop with the in-box MCP client bridge (0.2.0-rc.2 or newer), uv on the PATH of the process running DSH, and a model that accepts image input if you want the agent to actually see screenshots. On first start uvx builds an isolated environment for Windows-MCP, downloading tens of MB of Python dependencies that can take minutes on a slow connection; the bridge waits roughly a minute per launch and then retries, so a cold start may take a few attempts before the tools appear. Switch the Computer Use pill on when you want the agent to drive the desktop, and off when you do not — the tools disappear from the visible list immediately.

How to Troubleshoot This Plugin?

When the mcp__windows__* tools do not show up, call the plugin's own windows_mcp_doctor tool: it explains what is wrong and reports whether the Computer Use switch is on or off. If the tools take a while to appear, it is usually the first cold start still downloading dependencies, so wait and retry as described in the official instructions.