H
Hutusion/dsh-cua
An MCP server + agent skill for computer use on Windows: accessibility element actions come
★ 9·更新 2026-10-06
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 9 ★ · Hutusion/dsh-cua · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 9 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Hutusion/dsh-cua;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# dsh-cua
以下摘录自该仓库的 README(片段)
English · 中文
An MCP server + agent skill for computer use on Windows: accessibility element actions come
first and screenshots are only the fallback. It ships a cross-session arbiter — when several
agents share one machine it serializes them, and it yields while you are actually using the
computer yourself.
This repository contains only the MCP server and the skill. It stays neutral toward any stdio
MCP client (dsh / Claude Code / Codex / Cursor / Cline / ZCode …) — nothing here requires dsh.
Platform semantics (0.3.1 and later): the tools only work on Windows — they drive
user32/kernel32 and UI Automation. But the package also imports elsewhere and the server
starts there, answering tools/list as usual, so any client or directory crawler can
enumerate all 19 tools with their full schemas; actually calling a tool returns a clear
"requires Windows" error rather than the process failing to start at all. In 0.3.0 the import
itself raised, which made such crawlers unable to see the server at all
(tests/linux-handshake.py is the regression test for this property, and CI runs it on
ubuntu-latest).
## What it is
A stdio MCP server exposing 19 tools. Every tool name is prefixed tool_, exactly as
tools/list returns it.
Observe (read-only, callable at any time): tool_skyshot (reads a window as a compact,
diffable text tree — three orders of magnitude smaller than a screenshot), tool_element_at_point,
tool_read_element, tool_find_elements, tool_capture_window (DPI-aware, cropped to the client area),
tool_list_windows / tool_find_window / tool_get_window_rect, tool_list_displays, tool_cursor_position,
tool_clipboard_read, tool_coexistence_status
Element actions (soft gate: serialized across agents, no physical input injected):
tool_element_action / tool_element_action_at — press / set_value / select / toggle / expand /
collapse / scroll_into_view / focus, delivered straight to the UIA element, so they
never steal focus and never care about z-order
Other mutating calls (soft gate too: the mutex, but no human-contention yield):
tool_type_text (targeted PostMessage with effect_verified), tool_clipboard_write,
tool_open_application. They
synthesize no physical input, so they do not wait for you to stop working — and a clipboard
write still destroys whatever you last copied, so announce it when you do.
Physical input (hard gate: serialized across agents and yields to the human): exactly two
things share your one cursor and one keyboard — tool_click_at's raw_event path and
tool_send_keys' global hotkeys. The gate waits for the machine to go input-quiet, then refuses
with user-active rather than fight you for the cursor. tool_click_at tries its element path
first (ax_press), which injects no physical input and therefore takes the mutex only; the
receipt's method field says which path actually ran.
"Read-only" here means it takes no mutating action and synthesizes no input, so it is safe to
call while someone is using the machine. Two of them have a side effect worth knowing:
tool_capture_window writes the screenshot to disk (save_path; a temp file when omitted), and
tool_skyshot updates the server-side diff baseline it diffs the next shot against.
An MCP server + agent skill for computer use on Windows: accessibility element actions come
first and screenshots are only the fallback. It ships a cross-session arbiter — when several
agents share one machine it serializes them, and it yields while you are actually using the
computer yourself.
This repository contains only the MCP server and the skill. It stays neutral toward any stdio
MCP client (dsh / Claude Code / Codex / Cursor / Cline / ZCode …) — nothing here requires dsh.
Platform semantics (0.3.1 and later): the tools only work on Windows — they drive
user32/kernel32 and UI Automation. But the package also imports elsewhere and the server
starts there, answering tools/list as usual, so any client or directory crawler can
enumerate all 19 tools with their full schemas; actually calling a tool returns a clear
"requires Windows" error rather than the process failing to start at all. In 0.3.0 the import
itself raised, which made such crawlers unable to see the server at all
(tests/linux-handshake.py is the regression test for this property, and CI runs it on
ubuntu-latest).
## What it is
A stdio MCP server exposing 19 tools. Every tool name is prefixed tool_, exactly as
tools/list returns it.
Observe (read-only, callable at any time): tool_skyshot (reads a window as a compact,
diffable text tree — three orders of magnitude smaller than a screenshot), tool_element_at_point,
tool_read_element, tool_find_elements, tool_capture_window (DPI-aware, cropped to the client area),
tool_list_windows / tool_find_window / tool_get_window_rect, tool_list_displays, tool_cursor_position,
tool_clipboard_read, tool_coexistence_status
Element actions (soft gate: serialized across agents, no physical input injected):
tool_element_action / tool_element_action_at — press / set_value / select / toggle / expand /
collapse / scroll_into_view / focus, delivered straight to the UIA element, so they
never steal focus and never care about z-order
Other mutating calls (soft gate too: the mutex, but no human-contention yield):
tool_type_text (targeted PostMessage with effect_verified), tool_clipboard_write,
tool_open_application. They
synthesize no physical input, so they do not wait for you to stop working — and a clipboard
write still destroys whatever you last copied, so announce it when you do.
Physical input (hard gate: serialized across agents and yields to the human): exactly two
things share your one cursor and one keyboard — tool_click_at's raw_event path and
tool_send_keys' global hotkeys. The gate waits for the machine to go input-quiet, then refuses
with user-active rather than fight you for the cursor. tool_click_at tries its element path
first (ax_press), which injects no physical input and therefore takes the mutex only; the
receipt's method field says which path actually ran.
"Read-only" here means it takes no mutating action and synthesizes no input, so it is safe to
call while someone is using the machine. Two of them have a side effect worth knowing:
tool_capture_window writes the screenshot to disk (save_path; a temp file when omitted), and
tool_skyshot updates the server-side diff baseline it diffs the next shot against.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/hutusion-dsh-cua/)
- 来源
- awesome · https://github.com/Hutusion/dsh-cua
- 按领域浏览
- MCP 服务
- Traction
- 9 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。