glass
Related Servers
Alternatives to glass
- AlicenseAqualityNot gradedmaintenanceEnables browser automation through Playwright using accessibility tree snapshots instead of screenshots. Supports web scraping, form interactions, testing, and connecting to existing browser sessions with logged-in accounts.239,525 npm5-
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides powerful inspection and interaction tools for connected android devices or emulators.11MIT
- AlicenseBqualityDmaintenanceEnables AI agents to inspect, log, and control React Native apps on Android emulators or iOS simulators, including UI tree, tap, scroll, and hot reload.22576 npm5MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to build, drive, and observe Android/KMM apps end-to-end through ADB and Gradle, with tools for UI automation, error capture, and testing.3343 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables driving a Quickshell QML app inside a headless compositor, with tools to screenshot windows, inspect their object trees, and read or write QML state.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI-powered automation, debugging, and observability of Electron applications through Chrome DevTools Protocol integration, providing real-time UI interaction and inspection capabilities.172 npm23MIT
- AlicenseNot gradedqualityAmaintenanceAn embedded, cross-platform Model Context Protocol bridge for testing and automating GPUI applications.8Apache 2.0
TDQS
Scored across 31 tools
Most tools are clearly separated by target and action: click vs click_element, type vs set_value, and the wait_for_* variants are distinguishable. A few pairs (screenshot/a11y_snapshot, click/click_element, wait_stable/wait_for_region) could still be mis-selected by an agent skimming descriptions, but each has a precise purpose.
All names share the glass_ prefix and snake_case, but the pattern is mixed: many are verb_noun (select_window, wait_for_element) while others are bare nouns (logs, doctor), verbs (click, type), or reversed noun_verb (baseline_save, clipboard_get). Still readable and navigable, but not a consistent verb_noun convention.
31 tools crosses the 25+ threshold and is more than double the well-scoped range. The granularity (several wait variants, clipboard get/set, separate click vs click_element) may be useful, but the surface is heavy and could be consolidated.
The set covers the full UI-automation lifecycle: start/stop, window management, input, semantic and pixel observation, baselines, logs, clipboard, and diagnostics. Minor gaps like no direct hover/double-click convenience or element-attribute introspection are easily worked around with move/click/wait, so there are no dead ends.