日本語 English

Windows用のコンピュータ使用MCPサーバー Claude、Cursor、または任意のMCPクライアントは、Windows 10 / 11デスクトップを見、操作してみましょう — スクリーンショット、UIオートメーション、Chrome CDP、キーボード/マウス、ターミナル — ピクセル座標推論を回避する**と、per-action perceptionは、それが起こる前に誤ったウィンドウタイピングをキャッチするです。

32 ツール、ネイティブ Rust エンジン(UIA 2 ms)、ゼロコンフィグ PowerShell フォールバック、完全な CJK サポート、MIT ライセンス。 上記のスニペットをClaude / Cursor / VSコードコピロットコンフィグに追加し、Claudeは、メモ帳、Excel、Chrome、Windowsターミナル、およびその他のアプリをマシンに駆動できます。

ピクセルクリックでなぜですか? 2つのアイデアは、すべてのツールを介して実行します。discover-then-act — [desktop_discover]は、生の座標ではなく、短命のリースでインタラクティブなエンティティティティティティティティを返し、 [desktop_act]]は、あなたが意味する何で動作します。それは、それがなかった場所*、およびper-action perceptionガードは、ターゲットウィンドウのアイデンティティとバインドを検証し、間違ったウィンドウのタイピングをキャッチし、それらが起こる前にストル座標がクリックします。 ツイート **2.

desktop-touch-mcp

日本語

Computer-use MCP server for Windows. Lets Claude, Cursor, or any MCP client see and operate your Windows 10/11 desktop — screenshots, UI Automation, Chrome CDP, keyboard / mouse, terminal — with semantic discover-then-act targeting that avoids pixel-coordinate guessing, and per-action perception guards that catch wrong-window typing before it happens.

npx -y @harusame64/desktop-touch-mcp

32 tools, native Rust engine (UIA in 2 ms), zero-config PowerShell fallback, full CJK support, MIT licensed. Add the snippet above to your Claude / Cursor / VS Code Copilot config and Claude can drive Notepad, Excel, Chrome, Windows Terminal, and any other app on your machine.

Why this over pixel-clicking? Two ideas run through every tool: discover-then-act — desktop_discover returns interactive entities with short-lived leases instead of raw coordinates, so desktop_act operates on what you mean, not where it was — and per-action perception guards that verify the target window’s identity and bounds before input lands, catching wrong-window typing and stale-coordinate clicks before they happen.

2.1 reads UI Automation by element count instead of depth: Chrome, Edge and VS Code pages, Explorer and Settings values, and Word’s body are read and can be acted on, and what UIA still cannot see falls back to OCR and Set-of-Marks as before. desktop_act also types into Word’s body, and into Windows Terminal after asking the user. 2.0 refuses an action that cannot be done, with a reason, instead of reporting it done, and an action aimed by hwnd reaches that window only. See the CHANGELOG.

---

Features

• 🔁 Every act reports what it did — desktop_act answers with what changed: elements that appeared or disappeared, a modal, a focus move, the screen’s repaint (observation), and with narrate:"rich" the values and names that changed. The agent reads the result of its click from the reply instead of taking another screenshot. On UIA-blind targets it can also attach a PNG of just the region that changed (roiCapture; on by default for a visible change, returnCapture:"never" to suppress, "always" to force).
• 🛑 An act that cannot be done is refused, not reported as done — input that would not reach the field, a window blocked by a dialog, a closed window, a window on another virtual desktop: nothing is sent, and the reply names the reason and what to do next. An act aimed by hwnd never lands in another window with the same title.