Glasswarp
OfficialRelated Servers
Alternatives to Glasswarp
- AlicenseAqualityAmaintenanceWindows desktop automation MCP server — screenshot, mouse, keyboard & UI Automation. Lets LLM agents see and control your Windows desktop directly.30796 npm22MIT
- AlicenseAqualityCmaintenanceAllows AI clients to see and control Windows 10/11 desktops via MCP, with screenshots, UI Automation, Chrome CDP, keyboard/mouse, and terminal using semantic element targeting.30796 npmMIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to see and operate a Windows PC through mouse, keyboard, screenshots, OCR, window control, and shell commands.-
- AlicenseNot gradedqualityAmaintenanceRealtime PC eyes and hands for any AI agent — provides desktop, browser, file, registry, and OS control via batched execution and lease-based safety gates.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI models to control a local Windows desktop by moving the cursor, clicking, scrolling, typing Unicode text, sending key chords, and capturing screenshots. Runs natively on Windows with minimal latency and no heavy dependencies such as Python, PyAutoGUI, or Docker.75 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to autonomously control Windows 11 and 10 desktops via sub-10ms screen capture, native UI Automation element inspection, and zero-lag keyboard and mouse input. Combines a visual plane with a semantic plane and stall detection so agents can operate real applications reliably without vision-only guessing.13 npm40 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to see and control your desktop with tools for screenshots, clicks, typing, and more, all locally on macOS and Windows.180 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to observe and control the user's live desktop by listing apps, reading accessibility trees, and performing clicks, typing, scrolling, dragging, and other input actions with per-action approvals and local audit archives.1MIT
TDQS
Scored across 16 tools
Each tool has a clear, distinct purpose. Even similar tools like click_target and click_xy are differentiated by description, and type_text vs send_keys serve different input needs. No overlapping or ambiguous tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., end_session, click_target, list_rigs, send_actions). The only exception is 'observe', but it stands alone as a single-word verb. No mixing of conventions.
With 16 tools, the set is slightly above the typical 3-15 range but each tool serves a necessary function for remote desktop control. It could be trimmed, but the count is still reasonable and not excessive.
The tool set covers the full lifecycle: session management (start/end/status), UI observation and input (click, type, keys, drag, scroll, batch actions), app launch, and configuration (list rigs/demos, live view URL). No obvious gaps for the domain.