Skip to main content
Glama

Related Servers

Alternatives to wayland-computer-use-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to automate Linux desktop GUI by launching and interacting with Wayland applications in isolated virtual KWin sessions, or connecting to live desktops for collaborative automation.
      159 PyPI
      81
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate a real GNOME Wayland desktop through accessibility-tree widget actions, pointer/keyboard input, OCR, window management, and screen capture, optionally on a private headless session.
      33
      28 PyPI
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to see and control a Linux desktop via Wayland/Hyprland, providing screenshots, structured desktop state, pointer/keyboard input, semantic window/workspace tools, and a policy engine for safe execution.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate and observe Linux desktop GUIs on KDE Plasma 6 Wayland through isolated virtual sessions or live desktop connections, providing 30 tools for input, clipboard, accessibility tree inspection, screenshots, and window management.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate a Linux desktop natively on Wayland, with 68 tools for screen capture, input simulation, browser automation, OCR, accessibility, media, audio, clipboard, notifications, filesystem, system, memory, and network operations through the MCP protocol.
      MIT

    TDQS

    B3.1/5.0

    Scored across 22 tools

    Disambiguation3/5

    Several tools overlap heavily: interact_with_node already supports click, double_click, right_click, hover, type, set_value, and clear, yet there are separate click/double_click/right_click/hover/type_text/key_combination tools, leaving the agent to guess whether to target a semantic node ID or raw coordinates. batch_actions and preset_workflow also both execute step sequences, differing only in persistence. Descriptions help (AT-SPI vs coordinate fallback), but boundaries remain fuzzy.

    Naming Consistency3/5

    Everything is snake_case, but the conventions are mixed: verb_noun (launch_app, inspect_ui_tree, capture_window_frame), bare verbs (click, hover, drag, scroll), noun_verb (clipboard_read, clipboard_write), and noun phrases (window_control, batch_actions, preset_workflow). Readable but not a single predictable pattern.

    Tool Count3/5

    At 22 tools the surface is on the heavy side for the domain, and much of that weight comes from the low-level mouse/keyboard primitives that duplicate what interact_with_node and batch_actions already do. The app-lifecycle and clipboard groups clearly earn their place, but the input layer could be consolidated.

    Completeness4/5

    Coverage is broad for a Wayland computer-use server: window state, app lifecycle with logs, accessibility tree inspection, semantic and raw input, batching, presets, UI event watching, frame capture, and clipboard read/write. Minor gaps exist around window enumeration/positioning and full-screen (non-window) capture, but core agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues