Skip to main content
Glama
claude-background-control

claude-background-control

Related Servers

Alternatives to claude-background-control

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to drive macOS apps in the background through the computer-use engine bundled with the ChatGPT desktop app, sending clicks, drags, keystrokes, menu bar and notification interactions to target apps while the user's cursor, windows and other work stay untouched.
      6 npm
      6
      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.
      12 npm
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling macOS apps in the background, letting Claude Code or Codex act on native app UI elements without foregrounding them.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to inspect and drive native macOS app UIs during development via an in-process view tree and screenshot renderer, without requiring screen recording permission.
      7
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Lets Claude Desktop and Claude Code inspect and drive Windows desktop applications in the background, including clicking, typing, launching, and verifying results, while the user keeps their mouse, keyboard, and foreground window.
      7
      176 PyPI
      4
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (drag, key, scroll, inspect, screenshot, wait_for), and the descriptions actively steer between the overlapping pairs: type vs set_value (frontmost/paste vs background/accessibility) and click vs click_element (raw coordinates vs accessibility target). These pairs remain somewhat confusable at a glance, but the guidance resolves them, so only minor ambiguity remains.

    Naming Consistency3/5

    Everything is snake_case, but the convention is mixed: some names are verbs (drag, type, click, scroll, inspect) while others are bare nouns (menu, key, screenshot) or noun-verbs (click_element, set_value). It stays readable, but there is no single predictable verb_noun pattern.

    Tool Count5/5

    12 tools is well-scoped for a desktop GUI automation surface, with each tool covering a distinct primitive (input, navigation, inspection, capture) and none appearing redundant.

    Completeness4/5

    The set covers a broad automation lifecycle: launch/activate, inspect, click/type/key/set_value, scroll/drag, wait, and screenshot, with accessibility and coordinate fallbacks. Minor gaps exist (e.g. right-click/context menus, hover), but agents can work around them.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data