dsh-windows-mcp

Q: Does it collide with dsh-computers?

For dsh-windows-mcp the recommendation is dsh-computers: It is built for many machines rather than one OS surface; keep windows-mcp only if every target is Windows.

Q: What happens when dsh upgrades?

Nothing declares a version window for dsh-windows-mcp: dsh --version tells you what you are running, and no check will tell you whether dsh-windows-mcp matches it.

Windows desktop automation exposed to DSH as tools.

Version 0.2.10 of dsh-windows-mcp, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-windows-mcp writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-windows-mcp

Compatibility

dsh-windows-mcp ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

No peers and no dsh range, so no pre-check. It registers Windows automation tools next to whatever dsh-ops already provides; two tools with overlapping intent is a prompt-level conflict — the model may pick the weaker one.

Who made it

Author: helloHub1212. Repository: https://github.com/helloHub1212/dsh-windows-mcp. Package page: https://www.npmjs.com/package/dsh-windows-mcp.

After install

It declares no dsh peer and renders a new callable tool in the tool list; after dsh plugin add dsh-windows-mcp, dsh --profile web --dump-config lists the dsh-windows-mcp row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-windows-mcp, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing dsh-windows-mcp is the mirror command, dsh plugin --profile web remove dsh-windows-mcp. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with dsh-computers?

For dsh-windows-mcp the recommendation is dsh-computers: It is built for many machines rather than one OS surface; keep windows-mcp only if every target is Windows.

What happens when dsh upgrades?

Nothing declares a version window for dsh-windows-mcp: dsh --version tells you what you are running, and no check will tell you whether dsh-windows-mcp matches it.