Desktop Touch MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    if ((program === "sudo" || program === "doas") && privLaunchesInteractiveShell(rest)) return "interactive";

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const child = spawn(HELPER_EXE, ["-PipeName", pipeName, "-McpPid", String(mcpPid)], {

  fs.writeFileSync(path.join(root, file), data, { mode: 0o600, flag: "wx" });

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update SHA256 in launcher.js
        env:
          SHA256: ${{ steps.sha.outputs.sha256 }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add desktop-touch-mcp -- npx -y @harusame64/desktop-touch-mcp

{
  "mcpServers": {
    "desktop-touch-mcp": {
      "args": [
        "-y",
        "@harusame64/desktop-touch-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.desktop-touch-mcp]
command = "npx"
args = ["-y", "@harusame64/desktop-touch-mcp"]

{
  "mcpServers": {
    "desktop-touch-mcp": {
      "args": [
        "-y",
        "@harusame64/desktop-touch-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "desktop-touch-mcp": {
      "args": [
        "-y",
        "@harusame64/desktop-touch-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DESKTOP_TOUCH_AUTO_GUARD (Set to '0' to disable automatic action guards (reverts to v0.11.12 behavior).), DESKTOP_TOUCH_PERCEPTION_RESOURCES (Set to '1' to enable MCP perception resources.), DESKTOP_TOUCH_PERCEPTION_IDLE_MS (Idle ms before the WinEvent sidecar enters dormancy (default 60000).), DESKTOP_TOUCH_PERCEPTION_DORMANCY_DISABLE (Set to '1' to keep the WinEvent sidecar always running (no auto-dormancy).), DESKTOP_TOUCH_DIAGNOSTIC_LOG_DISABLE (Set to '1' to disable the JSONL diagnostic event log (issue #365 Phase 2).), DESKTOP_TOUCH_DIAGNOSTIC_LOG_PATH (Override path for the diagnostic event log.), DESKTOP_TOUCH_RESOLVE_LOG_RAW (Set to '1' to record window titles and title queries in clear in the diagnostic event log. Off by default: titles are recorded as a short hash plus their length, because a title can contain a file name, a mail subject, or a browser page title.). The author declared them in the registry entry; get the values from the project itself.