Glass vs Desktop Touch Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
G
Glass
fixed-width
🖥️ OS Automation
D
🖥️ OS Automation
SummaryGives a coding agent a build → see → interact → debug loop over the native GUI app it is writing: launch the app, screenshot it, read its accessibility tree, inject mouse/keyboard/gestures, tail its logs, and diff frames to confirm a change landed. Drives apps as an external black box with no app integration, so any toolkit or language works. 30 tools with text-first responses (element ids, diffs, waits) so the agent need not screenshot every step, plus optional sandboxing of the launched app. Backends: X11, Wayland, Windows, macOS, Android emulators, and the iOS Simulator.Windows desktop automation for LLM agents with entity-based actions instead of coordinate-only clicking. Uses UIA, CDP, screenshots, keyboard/mouse/clipboard, and terminal control, plus entity leases, verified delivery, causal context, and interaction memory to reduce silent UI automation failures.
Quality signal27/100 (Emerging)23/100 (Emerging)
Install pathnpx · lownpx · low
Engagement 0 0 0 10 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView GlassView Desktop Touch Mcp
More alternatives to GlassMore alternatives to Desktop Touch McpOS Automation category

Other servers like Glass