日本語

Windows电脑MCP服务器。 让Claude、光标或任何MCP客户端能够通过语义发现后行动的目标锁定来查看并操作你的Windows 10/11桌面——截图、UI自动化、Chrome CDP、键盘/鼠标、终端——并支持语义发现后行动的定位*，避免像素坐标猜测，以及按动作感知防护*，能在错误窗口输入发生前发现。

32个工具，原生Rust引擎（UIA只需2毫秒），零配置PowerShell备份，完全支持中日韩，MIT授权。把上面的片段添加到你的Claude/光标/VS Code副驾驶配置中，Claude就能驱动记事本、Excel、Chrome、Windows终端以及你机器上的任何其他应用。

为什么选择像素点击而不是像素点击？ 每个工具都有两个理念：发现-然后行动 — desktop_discover 返回的交互实体只用短暂租约而非原始坐标，所以 desktop_act 是基于你说的内容，而不是它曾经的位置操作——以及**按动作感知守卫*，在输入落点前验证目标窗口的身份和边界，及时捕捉错误窗口输入和陈旧坐标点击。

**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.