Desktop MCP vs Desktop Touch MCP
A side-by-side look at the Desktop MCP and Desktop Touch MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Desktop MCP for os automation work as a local process; choose Desktop Touch MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Desktop MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Choose Desktop Touch MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
DESKTOP_TOUCH_MCP_HOME, GITHUB_TOKEN, GH_TOKEN, DESKTOP_TOUCH_MCP_ALLOW_UNVERIFIED. - You want tools like
desktop_discover, desktop_act, desktop_state.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 37/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | DESKTOP_TOUCH_MCP_HOMEGITHUB_TOKENGH_TOKENDESKTOP_TOUCH_MCP_ALLOW_UNVERIFIED |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 22 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 23 |
| Full listing | View Desktop MCP | View Desktop Touch MCP |
Tools & capabilities
Desktop MCP tools
No tool names declared yet. Check the project README from the listing page.
Desktop Touch MCP tools 23
desktop_discoverObserve the desktop. Returns interactive entities with leases (UIA, CDP, Terminal, Visual SoM).desktop_actPerform actions (click, type, set a value, select) on entities via lease validation. Returns semantic diffs — plus an optional `roiCapture` (changed-region PNG + next-target preview) on visual-only targets.desktop_stateLightweight check of focus, active window, cursor, and Auto-Perception attention signal.screenshotMulti-mode capture: `detail='text'` (UIA/OCR), `diffMode` (P-frame), `dotByDot` (1:1), and `background`. Returns a cheap `screenshot://by-ref/{id}` link to the saved image instead of inlining pixels every time.screenshot_queryInspect and prune the on-disk screenshot cache behind the by-ref links: `screenshot_query` lists saved captures without re-reading pixels; `screenshot_gc` reclaims space by retention policy (dry-run by default).workspace_snapshotInstant session orientation: all window thumbnails + UI summaries in one call.server_statusDiagnostic check for native engine health and feature activation.keyboardSend keyboard input. Supports background input (WM_CHAR) and IME-safe clipboard bypass.mouse_clickPrecision coordinate-based interaction with homing and force-focus protection.scrollMulti-strategy: `raw` (notches), `to_element`, `smart` (virtual lists), and `capture` (stitch).click_elementLegacy UIA-based click by name/ID (fallback when entities are unavailable).browser_openIdempotent debug-mode launch and reliable navigation.- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Desktop MCP
{
"mcpServers": {
"desktop-mcp": {
"command": "uvx",
"args": [
"desktop-mcp"
]
}
}
}
Desktop Touch MCP
{
"mcpServers": {
"harusame64-desktop-touch-mcp": {
"command": "npx",
"args": [
"-y",
"@harusame64/desktop-touch-mcp"
],
"env": {
"DESKTOP_TOUCH_MCP_HOME": "YOUR_DESKTOP_TOUCH_MCP_HOME_HERE",
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
"GH_TOKEN": "YOUR_GH_TOKEN_HERE",
"DESKTOP_TOUCH_MCP_ALLOW_UNVERIFIED": "YOUR_DESKTOP_TOUCH_MCP_ALLOW_UNVERIFIED_HERE"
}
}
}
}
Frequently asked questions
Desktop MCP is categorized under OS Automation and uses a local stdio subprocess. Desktop Touch MCP belongs to OS Automation and uses a local stdio subprocess. Pick Desktop MCP for os automation work and Desktop Touch MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Desktop MCP has no declared pricing — check the project's own site. Desktop Touch MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add desktop-mcp and harusame64-desktop-touch-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Desktop MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Desktop Touch MCP has 65/100 (Great) with 2 views, 0 installs and 22 GitHub stars.