Deskwright

Name: Deskwright
Author: tristanmuzzu

作者：tristanmuzzu版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.tristanmuzzu/deskwright

安装

概览

作者提供的说明（英文原文）

Agents use real GNOME/Wayland apps: on your screen, or an invisible second desktop you never see

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： DESKWRIGHT_SESSION, DESKWRIGHT_INPUT_BACKEND

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "deskwright": {
      "command": "uvx",
      "args": [
        "deskwright"
      ],
      "env": {
        "DESKWRIGHT_SESSION": "your-value",
        "DESKWRIGHT_INPUT_BACKEND": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add deskwright --env DESKWRIGHT_SESSION=your-value --env DESKWRIGHT_INPUT_BACKEND=your-value -- uvx deskwright

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "deskwright": {
      "command": "uvx",
      "args": [
        "deskwright"
      ],
      "env": {
        "DESKWRIGHT_SESSION": "your-value",
        "DESKWRIGHT_INPUT_BACKEND": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "deskwright": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "deskwright"
      ],
      "env": {
        "DESKWRIGHT_SESSION": "your-value",
        "DESKWRIGHT_INPUT_BACKEND": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

DESKWRIGHT_SESSION env
Which desktop to drive: 'primary' (the screen you are looking at), 'headless' for an invisible virtual-monitor session, or 'headless: ' to pick one of several.
DESKWRIGHT_INPUT_BACKEND env
Force the input path: 'mutter' for GNOME's org.gnome.Mutter.RemoteDesktop (no consent dialog), 'portal' for org.freedesktop.portal.RemoteDesktop (one consent, then persisted). Auto-selected when unse…

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 tristanmuzzu 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32688 个服务器的 0%
发布到注册中心的时间比此分类中其他 32688 个服务器的 32% 更新
基础检查结果等于或优于此分类中其他 32688 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Deskwright 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, 御府和田玉在售作品查询

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

御府和田玉在售作品查询

作者：163yu.com

Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Deskwright

Computer use for AI agents on GNOME Wayland.

Let your coding agent use your Linux desktop. Or give it one of its own, so it stops stealing your mouse.

Install • What it can do • A desktop of its own • When something's off • Security

Claude Code can edit your files and run your commands. It can't open GIMP, click a button in a settings dialog, or read what a native app is showing you. On macOS and Windows it can, through computer use. On Linux that's still on Anthropic's list.

This fills the gap on GNOME. It's an MCP server plus a small shell extension, and it hands an agent the actual desktop: launching apps, reading widgets, clicking, typing, dragging, window management, OCR and screen recording. Any MCP client can drive it. Claude Code, Codex, Cursor, your own script.

The part people tend to like most: DESKWRIGHT_SESSION=headless runs all of it on a virtual monitor that isn't on any of your screens. Your agent gets a real GNOME desktop to work on, and it never takes your focus.

Linux hybrid beta: 0.2.0b1

The beta adds guarded native controls, exact multi-control queries, adaptive visual fallback and shorter verified execution batches. It supports GNOME Wayland; Windows is not implemented. See the interaction guide and measurements and limits.

For a new installation:

pipx install --system-site-packages 'deskwright==0.2.0b1'

deskwright-setup

For an existing pipx installation, pipx upgrade --pip-args='--pre' deskwright keeps its existing system-site-packages setting. Run deskwright-setup to copy the updated extension, then log out and back in if setup reports a changed extension. Restart the MCP connection to load the updated Python tools. A connection restart alone cannot reload GNOME Shell's extension.

Why this exists

Wayland deliberately stops an application from seeing or touching any other window. That's a good rule, and it's why xdotool, wmctrl and grim either do nothing on GNOME or fail in ways that look like your own mistake. Every Linux computer-use project I found either shipped a Docker container running X11, or quietly assumed X11 and broke.

So I went looking for what GNOME actually permits, and it turns out to be quite a lot, just not where anyone looks. Mutter answers D-Bus. AT-SPI, the accessibility layer built for screen readers, exposes every real widget in every running app with its name, its role and the action it performs. And a shell extension runs inside gnome-shell itself, where the rest lives.

That middle one matters more than it sounds. Pressing a widget's own accessibility action isn't a nicer way to click. It's a different thing: it can't miss, it survives the window moving, and it needs no pointer at all. An agent working this way stops guessing at coordinates, and stops taking a screenshot after every action to find out what happened.

Install

You need GNOME Shell on Wayland. Check with echo $XDG_CURRENT_DESKTOP $XDG_SESSION_TYPE, which should mention GNOME and wayland.

The lazy way: hand it to your agent

Open Claude Code, or Codex, or whatever you use, and say:

Set up https://github.com/tristanmuzzu/deskwright on this machine,

follow the AGENTS.md.

AGENTS.md is a runbook written for agents. Every command, how to check each one worked, the right package names for Debian, Fedora and Arch, and the handful of things that go wrong with their fixes. Your agent will ask you for a sudo password once and tell you to log out once. That's your whole involvement.

By hand: two commands and a logout

pipx install --system-site-packages deskwright

deskwright-setup

deskwright-setup narrates every step. It turns on the accessibility flag, installs the bundled shell extension, and tells you about any missing system package with the right install line for your distro, so you're never guessing at package names. It never runs sudo itself.

Then log out and log back in. Once. There's no way around this one: on Wayland, gnome-shell only picks up an extension at session start.

Last step, point your client at it:

claude mcp add deskwright --scope user -- deskwright

That's it. Ask your agent to open an app and it will.

Why --system-site-packages , and what breaks without it

PyGObject publishes no wheels to PyPI. It's a distro package everywhere (python3-gi, python3-gobject, python-gobject), so an isolated venv can't import it. Leave the flag off and you get a server that starts cleanly and then dies on the first click with input_backend_failed.

uvx has no equivalent flag, which is the only reason this says pipx. If you'd rather skip pipx, a plain python3 -m venv --system-site-packages followed by pip install deskwright works identically.

As a Claude Code plugin instead

The repo is also a plugin marketplace. It registers the server plus a skill that teaches an agent which tool to reach for first.

claude plugin marketplace add tristanmuzzu/deskwright

claude plugin install deskwright@deskwright

The plugin runs the server from its own checkout, so there's no pip install. You still need the system packages and the extension, so run the setup out of the checkout Claude Code cloned for you, once:

~/.claude/plugins/marketplaces/deskwright/bin/deskwright-setup

Then log out and back in, same as above.

From a clone, if you want to hack on it

git clone https://github.com/tristanmuzzu/deskwright

cd deskwright bin/deskwright-setup ./mcp_server.py --self-test

./mcp_server.py is the same entry point as the deskwright command, by the path older registrations already point at. CONTRIBUTING.md has the layout and which test suites need a real session.

Check it works

DESKWRIGHT_SESSION=headless deskwright --self-test

You want 18/18 passed. It runs on a virtual monitor rather than your screen, so it's safe to run while you're working. The first run takes about 20 seconds because it has to start a second gnome-shell.

Drop DESKWRIGHT_SESSION=headless and it tests your real desktop instead. Do that one while you're looking at the screen: the self-test injects real input, because it's checking the guards that refuse dangerous key combinations.

When something's wrong, ask your agent to call desktop_health. It answers in one line whether this desktop is usable, then says which mechanisms work right now and what each of them will actually do.

What it can do

41 tools. Each returns enough that you do not need a second call to work out what happened. The order below is the order an agent should reach for them. Use native controls and exact queries where useful, with screenshots and ordinary input for visual work or incomplete accessibility.

Tool	What it's for
`ui_apps`, `ui_tree`, `ui_find`	Find things. `ui_find` searches 30 levels deep by default, because GTK4 nests far deeper than you'd expect.
`ui_press`	Compatibility API for invoking a widget by index path. Requires `expect_name` or `expect_role`; inspect the resulting state. Prefer `ui_action` for native identity and modal guards.
`ui_observe`, `ui_snapshot`, `ui_query`, `ui_inspect`, `ui_action`, `ui_wait`	Bounded native references, guarded actions and exact completion checks. See semantic interaction.
`ui_set_text`	Compatibility API for writing by index path, with exact readback. Prefer `ui_action` for native references, current-value comparison and modal guards.
`ui_read_text`	Read a widget's contents. This is how you verify something worked.
`launch_app`	Start an app by desktop id and wait for its window, inside one call.
`screen_map`	Where everything is, in pixels: windows top of stack first, plus every pressable widget of the focused app with the point to click it at. Each carries a `ref: N` you pass straight to `ui_press` or `pointer_click`. No coordinates to copy, identity re-checked on use.
`pointer_click`, `pointer_move`, `pointer_drag`, `pointer_scroll`	Real pointer input in absolute screen coordinates. Pass `expect_window` and a click that would land somewhere else is refused, with the blocker named so you can redirect in the same call.
`pointer_path`	Draw a continuous curve through a list of screen points, with one button press, bounded duration and interruption checks. Requires a target window.
`window_at`, `pointer_position`	What a click at a point would hit, before you click it. And where the pointer is now, or an honest note that only the last position it set is known.
`find_text`	Where a visible string is, in screen coordinates. OCR, about 0.3s for a window, and no image in your transcript. This is the answer for Chrome, Electron and Qt, which expose almost nothing to `ui_find`.
`wait_for`	Wait for a window, a widget, some text, a focus change or the clipboard, instead of sleeping a guessed number of seconds.
`region_changed`	Wait for pixels to change. For what `wait_for` can't express, like a reply arriving or a spinner stopping.
`assert_state`	Pass or fail with evidence, so a long run can decide for itself that it's finished.
`do_steps`	A known sequence in one call, validated before anything runs, with per-step retry and one picture at the end, or at the step that broke.
`list_windows`, `activate_window`, `window_layout`, `window_manage`	Window list, focus and layout. `window_layout` cannot close windows; general `window_manage` retains close.
`screenshot`, `zoom`	A picture, or a full-resolution crop of one window, region or widget. `zoom` never scales, so small text stays readable.
`screencast`, `frames`	For anything that moves, because a still can't show motion. `frames` also reports a per-frame delta series, which is how you tell a smooth scroll from a juddering one.
`type_text`, `press_keys`, `hold_key`	Keyboard input through compositor keysyms, with focus proven before anything gets typed.
`clipboard_read`, `clipboard_write`	Pasting beats two thousand keystrokes, and reading back is how you check it arrived.
`journal`	The trail of everything the agent did: arguments, outcome, whether it landed, screenshot hashes. For reviewing an unattended run, or working out where you are after a context reset.
`desktop_health`	One line on whether this desktop is usable, then the detail.

A second desktop it uses while you work

An agent that needs your screen is only half useful. deskwright-headless starts a separate GNOME session on a virtual monitor, with its own session bus, its own gnome-shell --headless and its own runtime directory. A server pinned to it drives that desktop with the same 41 tools while you keep the physical one.

deskwright-headless start                    # about 200 MB of gnome-shell, idempotent

deskwright-headless status # live

只显示了开头部分；其余内容请在仓库中阅读

Deskwright

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

御府和田玉 在售作品查询

作者的 README

Deskwright

Linux hybrid beta: 0.2.0b1

Why this exists

Install

The lazy way: hand it to your agent

By hand: two commands and a logout

Check it works

What it can do

A second desktop it uses while you work

御府和田玉在售作品查询