Skillget

Desktop-Computer-Use

mcp
Security Audit
Warn
Health Warn
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 6 GitHub stars
Code Warn
  • network request — Outbound network request in scripts/settings_server.py
  • network request — Outbound network request in tests/chrome_context_menu_regression.py
  • network request — Outbound network request in tests/chrome_transient_dialog_regression.py
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Desktop Computer Use (DCU): background Windows computer-use MCP server that controls apps without moving the real cursor or stealing focus.

README.md

Desktop Computer Use (DCU)

License: MIT Latest release Platform: Windows

Desktop Computer Use, or DCU, is a background Windows computer-use MCP server. It controls desktop applications without moving your real cursor, stealing focus, or making the target application count itself as focused.

Use the short name DCU in agent instructions to distinguish it from built-in foreground computer-use tools:

Use DCU to control the Windows desktop in the background.

A cosmetic green virtual cursor shows DCU actions while you continue working normally.

Why DCU

Capability Result
Focus-free control Your active application, keyboard focus, and real cursor remain available.
UIA-first actions DCU uses accessibility patterns before window-message fallbacks.
Background screenshots It can capture many visible or occluded windows without activating them.
Observable actions Action results report detected effects instead of dispatch success alone.
MCP-native interface Claude Code, Codex, and other MCP clients can use the same tool contract.

The benchmark suite and current results are documented in docs/benchmarks.md.

Quick Start

Download dcu.exe from the latest release. It is a self-contained Windows executable and does not require a separate .NET installation.

Claude Code

claude mcp add dcu -- "C:\path\to\dcu.exe"

Codex or another MCP client

[mcp_servers.dcu]
command = 'C:\path\to\dcu.exe'

Run diagnostics at any time:

.\dcu.exe --doctor

Tools

Tool What it does
list_apps Lists running applications with visible windows.
get_app_state Returns an accessibility-tree snapshot, labeled elements, actions, values, and an optional annotated screenshot.
click Uses UIA patterns or a message click and reports an observed effect.
type_text Types through control messages or UIA value patterns.
press_key Posts a key or key combination.
scroll Uses the UIA scroll pattern, then a wheel-message fallback.
drag Performs a message-based drag with interpolated movement.
set_value Sets a value or toggle state directly.
wait_for Polls for text, elements, or window state on the server.
execute_sequence Runs several steps in one server-side batch.
hide_cursor Hides the cosmetic virtual cursor.

If more than one application matches a name or title, DCU returns an ambiguity error. Use the PID from list_apps to select the exact process.
| health_check | Checks the desktop session, UIA thread, and overlay. |

Settings

DCU reads settings.json next to the executable, then falls back to %APPDATA%\shadow-use\settings.json.

Security: Trust gates are disabled by default. DCU acts on the target you select, including password fields.

{
  "AllowUiaTextFallback": true,
  "EnableBoundsGuard": false,
  "EnableDesktopCheck": false,
  "ShowVirtualCursor": true,
  "EnableFocusGuard": true,
  "PostActionDelayMs": 150
}
Key Default Meaning
AllowUiaTextFallback true Allows UIA SetValue as a typing fallback. It can briefly foreground some applications.
EnableBoundsGuard false Refuses coordinate input when the window moved after the last snapshot.
EnableDesktopCheck false Refuses actions on the lock screen or secure desktop.
ShowVirtualCursor true Shows the green cosmetic cursor during actions.
EnableFocusGuard true Restores the foreground window and caret after an action takes them.
PostActionDelayMs 150 Wait time before the follow-up snapshot.

Run dcu-settings.bat to edit these settings in a browser and save them.

Build From Source

Requirements:

  • Windows
  • .NET 10 SDK
dotnet build src/ShadowUse/ShadowUse.csproj
dotnet run --project src/ShadowUse/ShadowUse.csproj -- --doctor

Windows shortcuts are also included:

setup.bat
run.bat --doctor
test.bat

Create a self-contained release executable:

dotnet publish src/ShadowUse/ShadowUse.csproj -c Release -r win-x64 `
  --self-contained true -p:PublishSingleFile=true -o publish

Architecture

Program.cs                 MCP stdio host; logs go to stderr
Config/Settings            settings.json loader
Automation/UiaThread       dedicated STA thread for UIA COM
Automation/UiaService      snapshots, element IDs, and re-resolution
Automation/BackgroundInput UIA-pattern-first input with message fallbacks
Capture/ScreenshotService  PrintWindow capture with bounded worker isolation
Overlay/VirtualCursorOverlay cosmetic cursor and click animation
Safety/Guard               optional bounds and desktop guards

Known Limits

  • Games and applications that read raw input or GetAsyncKeyState cannot see posted messages.
  • Modifier shortcuts do not always fire because posted messages do not update system-level modifier state. Chrome address-bar focus is handled through UIA as a verified exception.
  • A message click can rarely make an application activate itself.
  • PrintWindow fails on some hardware-accelerated applications. DCU then returns no screenshot by default instead of capturing an unrelated window from the visible screen.
  • The UIA text fallback can briefly foreground some applications.
  • Minimized windows do not have a capturable backing surface.
  • A non-elevated DCU process cannot control elevated targets.

Desktop Computer Use (DCU) — designed and built by dev-willbird1936.
MIT licensed. Keep the LICENSE and NOTICE files when redistributing or rebranding.

Reviews (0)

No results found