dsh-windows-mcp

Introduction¶

DeepSeek Harness (DSH) agents typically handle code or text files. When an agent needs to interact directly with the Windows desktop, for example by clicking UI elements, taking screenshots, or operating the clipboard, desktop automation capabilities are required. The dsh-windows-mcp plugin connects the CursorTouch/Windows-MCP protocol to DSH’s built-in MCP client bridge by mounting a one-line configuration, enabling the agent to “see” the screen and operate the computer.

Plugin Overview¶

This is a DeepSeek Harness plugin maintained by helloHub1212. It does not reimplement a protocol client or MCP SDK itself; instead, it is a “carrier bundle.” It uses DSH’s bundled @deepseek-ai/dsh-mcp-client bridge to start the Windows-MCP service via uvx, thereby exposing desktop operation tools.

Core Features¶

After installation and connection, the following tools appear in the DSH agent tool list:

• Vision and status: mcp__windows__Screenshot (screenshot, as an attachment), mcp__windows__Snapshot (accessibility tree without image tokens), mcp__windows__DisplayInventory (display device enumeration), mcp__windows__ControlStatus (control loop status; this tool cannot be disabled).
• Input operations: mcp__windows__Click, Move, Scroll (mouse), mcp__windows__Type, Shortcut (keyboard).
• Waiting and extraction: mcp__windows__Wait, WaitFor (wait conditions), mcp__windows__Scrape (extract window text).
• Batch and clipboard: mcp__windows__MultiSelect, MultiEdit (batch operations), mcp__windows__Clipboard (read/write clipboard).
• System and processes: mcp__windows__Process (process management), mcp__windows__Notification (notification reading), mcp__windows__Registry (registry read/write).
• Helper tools: windows_mcp_doctor (diagnostic tool for checking configuration and registered tools).

Additionally, a Computer Use pill marker appears next to the DSH Composer panel. It displays the number of registered desktop tools and retains state after restart (the file is located at ~/.dsh/dsh-windows-mcp.state.json). This feature is disabled by default.

Installation and Enablement¶

1. Install the plugin¶

Install it using the DSH plugin manager:

dsh plugin --profile <profile> add github:helloHub1212/dsh-windows-mcp

In DSH Desktop: go to Settings → Plugins, add the bundle (pointing to the released package name, the repository github:helloHub1212/dsh-windows-mcp, or a local checked-out directory), then restart DSH.

2. Install dependencies¶

Windows-MCP is a Python program. On the Plugin Settings page, click the Download and install button. This operation runs uv tool install windows-mcp@<pinned> in the background. After a successful installation, the plugin automatically writes the bridge configuration to cordis.patch.yml and prompts you to restart.

Usage Instructions¶

1. Verify the installation¶

Run the diagnostic tool:

windows_mcp_doctor

This command outputs the resolved uv/uvx/python paths, the ~/.windows-mcp status, the effective bridge configuration, and the actually registered mcp__windows__* tools.

2. Enable Computer Use¶

Find the Computer Use pill marker in the DSH interface.
* It is off by default.
* This is a hard switch, not a hint. When turned off, all mcp__windows__* tools are filtered at every step of the session and cannot be invoked.
* When turned on, the tools become available immediately.

3. Typical usage¶

After enabling Computer Use, you can ask the agent to perform tasks such as the following:

• “Capture my desktop and tell me what is on the screen.” (uses mcp__windows__Screenshot)
• “Open Notepad and type Hello World.”

Notes¶

1. Environment requirements:

   • Operating system: Windows 10 or 11.
   • DSH version: DSH Desktop 0.2.0-rc.2 or newer.
   • Dependencies: uv must be installed in PATH (DSH automatically searches %USERPROFILE%\.local\bin).
   • Model: A model that supports image input is required to effectively use the screenshot feature.

2. Feature limitations:

   • Default exclusions: mcp__windows__App (application launch/switching), mcp__windows__PowerShell, and mcp__windows__FileSystem are excluded by default (DSH itself already provides Shell and file tools, and App support is unstable on non-English systems).
   • Mandatory tool: mcp__windows__ControlStatus cannot be disabled.
   • Computer Use: It is a hard switch, not a soft hint.

3. Permissions and Profile:

   • The Electron desktop application has the desktop profile; the CLI refuses to execute any command against the desktop profile (including read-only commands). Use the GUI to configure desktop automation.

Conclusion¶

dsh-windows-mcp provides DeepSeek Harness with native Windows desktop automation by reusing DSH’s built-in bridge and the uvx toolchain. Through the Computer Use hard-switch mechanism, users can explicitly control the agent’s access to the desktop environment. For more details and source code, refer to the project homepage.

GitHub repository