ElfdeckAI
Related Servers
Alternatives to ElfdeckAI
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents local Linux desktop control through tools for screenshots, accessibility, mouse, keyboard, and reliable text input.36MIT
- AlicenseNot gradedqualityBmaintenanceEnables controlling your own Linux desktop machines from any MCP-capable LLM client, with opt-in agent capabilities for shell, filesystem, processes, screenshots, system info, and input injection.1MIT
- AlicenseAqualityBmaintenanceVerified control of the whole desktop for agents on Windows and Linux: apps with no API, windows, shell, browser. MCP server + CLI + REST API.3928MIT
- AlicenseNot gradedqualityCmaintenanceLinux desktop HAL for AI agents. One daemon, one socket, every desktop action. GNOME, KDE, Hyprland, X11. Ships in one command.31MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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 gradedqualityCmaintenanceAn MCP server that enables AI agents to observe and control a Hyprland Wayland desktop using screenshots, accessibility trees, native virtual pointer/keyboard input, and window management. It allows clicking, typing, scrolling, launching apps, and waiting for UI state without uinput, root, or portals, with an optional isolated nested desktop.2MIT
TDQS
Scored across 22 tools
Tools are mostly distinct by device and action, with clear separation between tap, hold, release, and safety-release operations. A few pairs (pad_center vs pad_reset, mouse_up vs mouse_release) overlap conceptually, but the descriptions help disambiguate them.
Names predominantly follow a snake_case device_action pattern (key_tap, pad_press, mouse_click), which is predictable. Minor deviations like mouse_move_to/mouse_click_at suffix forms and single-word screenshot/wait, plus the abbreviation hscroll, keep it from perfect consistency.
At 22 tools, the surface is on the heavy side for a general MCP server, and several granular hold/release/reset variants could feel excessive. Each tool does correspond to a real input primitive, but the count is borderline per typical scoping guidance.
The core input surface is comprehensive: keyboard, mouse, and gamepad tap/hold/release, analog sticks and triggers, recentering, screenshots, and timing. Minor gaps like text-entry (type_string) and multi-touch gestures exist, but there are no major workflow dead ends.