luda
Related Servers
Alternatives to luda
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA desktop automation MCP server that enables AI agents to interact with Linux environments through screenshots, window inspection, and input simulation. It provides tools for mouse control, keyboard input, and screen capture using xdotool and XDG Desktop Portals.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that gives a model eyes and hands on a Linux Wayland desktop, enabling screenshot capture, mouse/keyboard control, OCR, and icon detection via OmniParser.1-
- FlicenseAqualityAmaintenanceCross-platform desktop automation MCP server that lets AI agents capture screenshots, run OCR with UI-element classification, control mouse/keyboard, and launch programs on Linux, macOS, and Windows.201-
- AlicenseNot gradedqualityAmaintenanceMCP server for controlling Linux desktops over Wayland, enabling AI agents to perform mouse, keyboard, window, and screenshot operations on Fedora KDE Plasma.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server for reliable native macOS desktop control from AI agents, providing 72 tools for screenshots, mouse, keyboard, scroll, clipboard, window management, and more.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
Scored across 14 tools
Each tool targets a distinct desktop automation primitive: environment checks, window listing/activation, observation, accessibility inspection, text reading/writing/pasting, key chords, clicking, focusing, scrolling, dragging, and invoking actions. Even the input-related tools are clearly separated by mechanism and verification behavior.
All tools share the consistent desktop_ prefix and mostly use an imperative verb or verb_noun pattern (desktop_activate, desktop_read_text, desktop_press_keys). desktop_windows is the one noun-style outlier, and a few verbs like desktop_click and desktop_scroll lack an explicit object, but the overall convention is predictable.
Fourteen tools is well within the ideal range for a desktop automation server and each tool earns its place by covering a distinct interaction or observation need. The count feels appropriately scoped rather than bloated or thin.
The surface covers the core desktop workflow well: inspect, observe, activate, input, click, scroll, drag, and invoke. Minor gaps remain such as explicit window minimize/close/resize operations, mouse hover/right-click primitives, and direct clipboard access, but agents can typically work around these using the provided accessibility and keyboard tools.