Gnome Desktop Mcp vs Glass

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
🖥️ OS Automation
G
Glass
fixed-width
🖥️ OS Automation
SummaryGNOME desktop automation for AI agents. 30 tools via D-Bus: screenshots, window management, mouse/keyboard injection, clipboard, workspaces, and system notifications. Works on any GNOME 45–49 Linux desktop.Gives 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.
Quality signal21/100 (Emerging)27/100 (Emerging)
Install pathnpx · lownpx · low
Engagement 0 0 0 0 0 0 10
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Gnome Desktop McpView Glass
More alternatives to Gnome Desktop McpMore alternatives to GlassOS Automation categoryCanonical compare URL

Other servers like Gnome Desktop Mcp