omarchy-mcp
Related Servers
Alternatives to omarchy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to capture screenshots, inspect windows, and interact with the Hyprland desktop environment through mouse clicks and keyboard input.1-
- AlicenseAqualityBmaintenanceEnables AI agents to interact with the Linux desktop through desktop notifications, interactive dialogs, shell command execution, and privileged command execution.14 npm5MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and control an Omarchy/Hyprland desktop by taking screenshots, focusing windows, moving/clicking the mouse, scrolling, typing text, and sending keyboard shortcuts.MIT
- AlicenseNot gradedqualityDmaintenanceEnables full Linux desktop control including windows, mouse, keyboard, clipboard, audio, screenshots, OCR, accessibility, and system management through MCP-compatible AI agents.1MIT
TDQS
Scored across 108 tools
Most tools have clearly distinct purposes with detailed descriptions, but the sheer number creates some overlaps such as window_snap vs self_window_snap and layout_swap_windows vs window_swap. While these are functionally different, an agent may struggle to pick the right one in ambiguous situations.
The majority of tools follow a consistent verb_noun pattern (e.g., wifi_toggle, theme_set, window_close). Minor deviations exist, such as noun-based names like system_info and omarchy_version_info, but the style remains predictable and clear throughout the set.
With 108 tools, this server vastly exceeds any reasonable tool count for an MCP server. Even for a broad desktop environment, the number is overwhelming and will likely lead to tool-selection errors and increased latency. The scope is far beyond the typical 3-15 tools that are considered well-scoped.
The tool set covers an impressive range of desktop operations: themes, backgrounds, windows, audio, wifi, bluetooth, notifications, plugins, and more. There are minor gaps like explicit workspace creation, but hypr_dispatch offers flexibility. Overall, the surface is quite complete for the domain, with only a few missing lifecycle operations.