Windows desktop automation for AI agents: Anode, BgDesk, Windows-MCP, Desktop Touch MCP, windows-computer-use-mcp and Terminator compared

Checked on 24 October 2026: two of these six Windows desktop-automation MCP servers, Anode and BgDesk, run the agent in a separate Windows session (a child session) with its own pointer and keyboard focus, while Windows-MCP, Desktop Touch MCP, windows-computer-use-mcp and Terminator act in your own session, and each of those four has click paths that move your real pointer. We read the five besides Anode from their docs and source code and did not run them. A third route, used by Ghost, lowlevel-computer-use-mcp and computer-use-plus, drives apps with window messages (Ghost and computer-use-plus also use UI Automation), starting them on a hidden desktop in your session: by default it leaves your pointer alone, but some apps ignore message input. In Anode's live validation of version 0.11.1 (2 October 2026), with your real pointer over Anode's hidden viewer, Windows' Remote Desktop control tried 7 times to copy the agent's pointer moves to your pointer, and Anode blocked all 7; the 0.11.3 release passed its 112 quick checks for this page. Method, sources and data are below.

We make Anode. Read this as a vendor's page: our own numbers come from real runs that you can repeat, and everything about the other tools links to where we read it. If we got something wrong, open an issue and we will correct it.

First published 16 October 2026 · Last checked: 24 October 2026 · Anode release 0.11.3 (0836c78) · Next check by 23 November 2026, or sooner when one of these tools releases.

The short answer

Side by side

Anode's column is measured or taken from its own release record. The other columns are from each project's README, docs and source at the commit named under Sources, read on 24 October 2026, not run by us.

AnodeBgDeskWindows-MCPDesktop Touch MCPwindows-computer-use-mcpTerminator
Where the agent acts A second Windows session for your account (a child session), with its own screen; one seat, shared by your agents in turn A second Windows session for your account (a child session), its screen divided into up to 12 areas of 1440x900, one per agent Your session Your session Your session Your session
Your real pointer Not used by the agent; the seat has its own. Live check (0.11.1, your pointer over the hidden viewer): 7 of 7 copied pointer updates blocked Not used: real input goes to the child session's own pointer, or window messages for some app types; its README reports your pointer and foreground window unchanged in its tests Moved: Click calls SetCursorPos, then a mouse event Moved by mouse_click, mouse_drag, scroll (at a given point) and browser_click, and by desktop_act's DevTools and mouse routes; not by click_element (UI Automation Invoke only) Moved by its mouse tool and coordinate clicks in either mode (SetCursorPos and mouse_event); element clicks go through pywinauto, and the opt-in "background" mode tries Invoke first, then a real click Moved: click_element moves the real pointer with SendInput to click, then puts it back by default (restore_cursor); mouse_drag moves it, and its typing tools click the target, without putting the pointer back, when focusing fails; invoke_element doesn't move it
Your keyboard focus Not used; the seat has its own focus Not used; focus changes happen inside the child session Type clicks its target first; the App tool's switch brings a window to the front Its keyboard tool brings the window to the front by default, except background typing into terminal-class windows; optional forceFocus; browser_click brings the browser to the front Element text entry focuses the control (always by snapshot index, by selector when setting text fails); its keyboard tool types into whichever window has focus; its safety doc asks you to step back Action tools, invoke_element included, bring the target window to the front by default; most then restore your keyboard focus, but click_element and invoke_element leave it on the target unless restore_focus is set
How you take over or stop it anode show opens its viewer, where Take control lets you drive the seat; Ctrl+Alt+Shift+K or anode kill signs the seat out Take over any agent's area from a local web page (bgdesk workplace); the tray icon stops it; bgdesk down signs the session out A big mouse move or Ctrl+Alt+Shift+Backspace takes over (any input once the agent has been idle 15 s); new calls are refused until you've been idle 10 s Park the mouse in the top-left corner for 0.5 s Moving the pointer to the top-left corner aborts pointer actions; its mouse and keyboard tools refuse to act until approve_automation opens a window (5 minutes by default), a tool the agent can call itself; element clicks and text entry aren't gated A stop_execution tool cancels running tools; no hotkey or corner stop found
Signing in to the agent's session Automatic when Windows allows it; otherwise your Windows password in Windows' own dialog (a PIN may not work), not saved by Anode Windows' credential prompt at first start (an account with a password; a PIN doesn't count); the password is then kept in Credential Manager Not needed: your own session Not needed: your own session Not needed: your own session Not needed: your own session
MCP tools 41 (counted from tools/list) 13 (source) 21 (source) 32 (README) 20, or 22 with two opt-in tools (source) 35 (README and source)
Browsers Headed Chrome or Edge inside the seat, on its own profile Opens a URL in your default browser; Chromium browsers get their own data folder per area, without your logins; no DevTools protocol DOM mode through UI Automation: Chrome and Edge, and Firefox through an IAccessible2 fallback Chrome, Edge and Brave over the DevTools protocol (started with a debugging port) None built in; it suggests a separate Playwright server Through its Chrome extension, in your browser session
Android emulators Yes, booted inside the seat Not mentioned Not mentioned Not mentioned Not mentioned Not mentioned
Windows editions 10/11 Pro, Enterprise, Education, or Windows Server with the Remote Desktop host; not Home; x64 Windows 10 or 11, x64 (editions not named; other editions untested) Windows 10 and 11 (needs Python 3.14+; the 0.8.8 README still lists Windows 7 to 11) Windows 10/11 64-bit (editions not stated); a 4-tool macOS preview Windows 10 and 11 (editions not stated) Windows only (editions not stated)
Install install.ps1, then anode setup (one administrator prompt: Remote Desktop and child sessions) install.ps1 from its README (downloads the release), then bgdesk enable (administrator, once; its README: child sessions only) uvx windows-mcp serve (Python 3.14+, uv) npx -y @harusame64/desktop-touch-mcp (Node 20+) install.ps1 from its release (an MCPB bundle), or uv npx -y terminator-mcp-agent
Telemetry None None found in its source On by default (PostHog); ANONYMIZED_TELEMETRY=false turns it off None documented A local action log (SQLite); no remote analytics found On by default: PostHog usage analytics (always built in) and Sentry error reports (a default build feature); environment variables turn them off
Licence · stars · latest release MIT · 3 · 0.11.3, 18 Oct 2026 MIT · 5 · 2.0.0, 17 Oct 2026 MIT · 10,216 · 0.8.8, 10 Oct 2026 MIT · 22 · 2.3.2, 24 Oct 2026 MIT · 48 · 0.8.0, 10 Oct 2026 MIT · 1,659 · 0.24.32, 5 Apr 2026 (npm: 0.24.28)

What we measured on Anode

Two sources: a fresh run for this page, and Anode's own release record, where each live check names the script that repeats it.

Run for this page (24 October 2026)

To repeat it, in PowerShell:

gh release download v0.11.3 -R skulitom/Anode -p anode-windows-x64.zip -p SHA256SUMS
Get-FileHash anode-windows-x64.zip   # compare with SHA256SUMS (it prints upper case)
Expand-Archive anode-windows-x64.zip anode-0.11.3
.\anode-0.11.3\anode.exe selftest --quick | Out-Host

The first version of this page (16 October) measured main at 47feb59, before the 0.11.3 tag: 110 quick checks passed and 41 tools listed (output, tool list).

Live checks from Anode's release record

These ran in a real seat on Windows 11 Pro build 26200 (release record), with the viewer hidden except where noted:

Each tool, and when to choose it over Anode

Windows-MCP

CursorTouch/Windows-MCP is a Python MCP server with 21 tools, including Snapshot (the UI Automation tree), Screenshot, Click, Type, PowerShell, Registry and FileSystem. It is listed in Claude's connector directory. It works in your session: its Click moves the real cursor before pressing, and Type clicks its target first. Its 0.8.8 release (10 October 2026) added a control gate: during each call and for 15 seconds after it, it holds back your keyboard and mouse; a substantial mouse move or Ctrl+Alt+Shift+Backspace takes control back, and once the agent has been idle for 15 seconds any input does (so does any input while it hides its indicator to take a screenshot). It then refuses new calls until you have left the mouse and keyboard alone for 10 seconds. A screen edge and a cursor glow show when the agent has control, and its README calls the takeover best-effort. Its main branch has an opt-out and gate policies (#458, #466) that no release carries yet. Its security notes say it is not sandboxed and suggest a VM or Windows Sandbox. Anonymous telemetry is on until you set ANONYMIZED_TELEMETRY=false.

Choose it when you are happy to watch the agent work on your own desktop, are on Windows Home (where Anode can't run; Windows-MCP needs Python 3.14, which runs on Windows 10 and 11, and names no editions), want the most starred project here, or want shell, registry and file tools in the same server. To keep its tools while your own input stays in your session, where its gate shouldn't see it (so far tested with nobody at the PC), run it inside Anode's seat: Windows-MCP in the background. Choose Anode when you want to keep working while the agent clicks.

Desktop Touch MCP

Harusame64/desktop-touch-mcp is a TypeScript server with a native Rust core and 32 tools. It mixes routes. desktop_act tries UI Automation (Invoke and Value), then the DevTools protocol, which finds a browser element and clicks it with the real mouse, then terminal input (for Windows Terminal, a paste it asks you to approve each time), and finally a real mouse click at the element. click_element uses UI Automation Invoke only, which its guide says works without moving the cursor; since 2.3.2 its docs say not to use it on list, tree or grid items. mouse_click, mouse_drag, scroll at a given point and browser_click move the real mouse, animated by default; browser_click first brings the browser window to the front, and since 2.3.2 it refuses to click when another window covers the point. Its keyboard tool brings the target window to the front by default, except background typing into terminal-class windows, and a forceFocus option forces a window forward when Windows refuses. Parking the mouse in the top-left corner stops it.

Choose it for UI Automation-first work in your own session, Chrome pages over the DevTools protocol, terminal input, its Excel tool, or a macOS preview. Choose Anode when apps need real mouse and keyboard input and you don't want that input on your desktop.

windows-computer-use-mcp

sandraschi/windows-computer-use-mcp is a Python server built on pywinauto, with 20 tools (22 with two opt-in ones), plus a local web UI and a desktop app. Its mouse tool and coordinate clicks move the real pointer in either dispatch mode; element clicks go through pywinauto, and an opt-in "background" mode tries UI Automation Invoke first but falls back to a real click. Its mouse and keyboard tools are refused until approve_automation is called, which opens a 5-minute window by default (an environment variable bypasses it, and also turns off the corner abort below). The project calls this human-in-the-loop, but the agent can call that tool itself, so a person checks it only if your MCP client asks you to approve the call; element clicks and text entry aren't gated. Moving the pointer to the top-left corner aborts pointer actions. Its safety doc calls desktop automation "host-powerful", says the server doesn't start Windows Sandbox, and suggests a separate virtualisation server for isolation.

Choose it when you want an approval call before its mouse and keyboard tools, a local operator UI, or pywinauto's control coverage. Choose Anode when nobody should have to step away from the PC.

Terminator

mediar-ai/terminator is a Rust automation library with an MCP server (terminator-mcp-agent, 35 tools), from Mediar. Its README lists "Doesn't take over your cursor or keyboard" among its features. Its source at 73a381c shows that the click_element tool moves the real pointer with SendInput to click and then puts it back by default (restore_cursor), and that its action tools bring the target window to the front by default; most restore your keyboard focus afterwards, but click_element and invoke_element don't unless asked. mouse_drag moves the pointer too, and its typing tools click the target, without putting the pointer back, when focusing fails. invoke_element (UI Automation Invoke) is the route that doesn't move the pointer. A stop_execution tool cancels running tools, and a full-screen action overlay is on by default. PostHog usage analytics (always built in) and Sentry error reports (a default build feature) are on by default; environment variables turn both off. Its optional OmniParser and Gemini vision modes call Mediar's hosted service by default.

Choose it when you want its Rust automation library as well as the MCP server, its Chrome extension in your own signed-in browser, or Mediar's workflow builder and managed hosting for teams. Choose Anode when the agent's clicks and windows must stay off your desktop.

BgDesk

enwong93-sketch/background-computer-use (BgDesk, "Background Computer Use for Windows") is a C# MCP server, at release 2.0.0 since 17 October 2026, that uses the same Windows feature as Anode: a child session, a loopback Remote Desktop session under your own logon, turned on with WTSEnableChildSessions and hosted, off-screen, in Microsoft's Remote Desktop control. Its tagline says "hidden desktop"; its "How it works" section explains that this is a child session, a second desktop with its own input queue where SendInput works as it does for a person. That makes it a separate Windows session, not a hidden Win32 desktop like those of the tools under Hidden desktops and other routes. An agent process inside that session sends real mouse and keyboard input there, or window messages for app types it has tested (Chromium, Electron, Explorer, consoles and classic dialogs). The session's one large screen is divided into up to 12 areas of 1440x900, one per agent, so several agents can work at once. A local web page (bgdesk workplace, on 127.0.0.1 behind a token) shows each area live with a timeline of actions and lets you take an area over, and an ask_user tool hands logins, captchas and payments to you. It needs an account with a password and an administrator step once, and keeps the password in Windows Credential Manager after the first sign-in. Its README says bgdesk enable only turns on child sessions, leaving inbound Remote Desktop as you had it; Anode's setup also turns on the Remote Desktop listener, without opening the firewall. Its README lists its tests, run on Windows 11 Enterprise, says other editions are untested, and documents limits: no elevated windows, no whole-screen shortcuts, and message input that some controls ignore, which it checks for afterwards and can repeat as real input.

Choose it when several agents should work side by side, you want to watch and take over each one from a browser page, or you want later starts to sign in silently (it stores the password). Choose Anode when you need its wider tool set (UI Automation reads and waits, command jobs, display changes, audio, gamepads and Android emulators), a published record of live checks for each release since 0.9, with their scripts in its repository, or would rather type your Windows password when Windows asks than have it stored.

Anode's limits

Hidden desktops and other routes

In our discovery test of 22 October, AI agents asked to find a Windows MCP server that works in the background picked lowlevel-computer-use-mcp and computer-use-plus, and named Ghost and WindowsPC-MCP as alternatives (they also named BgDesk, in the table above). umbriel came up in a directory listing during our searches. All read from their README and source (umbriel from its README only) at the commits under Sources, not run by us.

Method

Sources

Read on 24 October 2026 at the commit shown. windows-computer-use-mcp, Terminator and umbriel were first read on 16 October 2026 and re-checked at the same commits on 24 October.