Skip to main content
Glama

Related Servers

Alternatives to macos-ui-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to read and operate macOS app interfaces through the accessibility tree, pressing buttons, setting text fields, typing with IME support, sending shortcuts, scrolling, dragging, and capturing screenshots. It drives background apps without moving the mouse or stealing focus from the user's current work.
      12
      608 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables high-speed native macOS automation for Claude by interacting directly with the Accessibility API, AppleScript, and UI trees instead of using screenshots. It allows users to read app states, click elements, and type text semantically across any macOS application.
      14 npm
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that lets Claude use your Mac — native apps and the browser — by remembering what it has seen instead of screenshotting every step.
      12
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect and control macOS apps via accessibility trees, screenshots, OCR, and input simulation, with a visible pointer.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to perceive and operate macOS applications through screenshots, on-device OCR, accessibility elements, and consent-gated input, and to run an app in an isolated virtual-display session with screenshots, OCR/ASCII frames, bounded history, and evidence reports. It supports text-only models via spatial text representations while keeping capture read-only by default and gating control behind macOS permissions and operator authorization.
      MIT

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: inspection (get_ui_tree, list_windows, screenshot), interaction (click, type, invoke_action), and synchronization (wait_for). No overlapping functionality; an agent can unambiguously select the right tool for a task.

    Naming Consistency4/5

    Most tools follow a verb-oriented pattern (get_ui_tree, list_windows, invoke_action, wait_for), while click and type are single verbs and screenshot is a noun used as a verb. The pattern is generally predictable, with only minor deviations from a strict verb_noun structure.

    Tool Count5/5

    Seven tools is well-scoped for a UI automation server. Each tool earns its place—reading state, capturing visuals, performing actions, and waiting—without unnecessary bloat or an overly sparse surface.

    Completeness4/5

    The surface covers the core UI workflow (inspect, interact, wait), but misses common operations like scrolling or keyboard shortcuts. These are not critical for many automation scenarios, so the set is mostly complete with minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues