No user-submitted related servers found.
Scored across 14 tools
Each tool has a crisply distinct role, and the descriptions actively delineate boundaries (pointer vs click_ui, keyboard vs use_bind vs hypr, screenshot vs zoom vs marks vs ui). Overlapping-seeming tools like screenshot/zoom/marks and ui/click_ui are separated by explicit coarse-to-fine vs accessibility vs annotated-capture semantics. An agent can reliably pick the right tool.
All names are lowercase single tokens with underscore used consistently for multi-word tools (wait_for, click_ui, use_bind), so formatting is uniform. The only wobble is semantic: some names are nouns (desktop, marks, binds, pointer) and others verbs (launch, zoom), which is a minor deviation from a single predictable pattern.
14 tools is well within the ideal 3-15 range and each earns its place: perception (desktop, screenshot, zoom, ui, marks), input (pointer, keyboard, click_ui), orchestration (wait_for, sequence), and system control (hypr, launch, binds, use_bind) with no filler.
The desktop-automation surface is essentially full: snapshot, capture at two fidelities, accessibility read/annotate, mouse, keyboard, background-window targeting, event waiting, window/workspace IPC, app launch, keybind discovery and replay, plus a batch runner. It even documents fallback paths (vision when no a11y tree) and hard limits (locked session, auth dialogs), leaving no obvious dead ends.