No user-submitted related servers found.
Scored across 17 tools
Most tools target distinct domains (apps, windows, browser tabs, cursor, permissions), but there are overlapping entry points: get_state duplicates app/window/browser listing, browser_manage broadly overlaps the browser_* family, and batch_execute vs js both serve multi-step orchestration. Descriptions help, but an agent can reasonably hesitate between these alternatives.
Names are consistently snake_case and grouped by prefix (browser_*, window-related), but the convention is mixed: some are verb_noun (list_apps, get_window_state) while others are noun_verb/noun phrases (window_action, browser_tab_state, cursor_control, batch_execute, browser_manage) and a few are bare nouns (permissions, js). Readable, but not a predictable verb_noun pattern.
17 tools is at the heavy end of the 3-15 guideline, and the surface includes broad mega-tools (browser_manage, window_action, browser_tab_action) alongside overlapping orchestration tools (batch_execute, js). Given the broad computer-use scope it is defensible, but it feels overloaded rather than tightly scoped.
Coverage is strong across macOS apps/windows, browsers, cursor overlays, batching, scripting, and permissions, with lifecycle management for windows and browser tabs. Minor gaps remain: no explicit app quit/terminate operation, and global system-level controls are absent, but agents can work around these via window/browser close or js.