Skip to main content
Glama
ServiceStack

omarchy-mcp

by ServiceStack

Related Servers

Alternatives to omarchy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables any LLM to fully control an Omarchy Linux desktop, including themes, apps, screenshots, reminders, audio, brightness, and Hyprland window tiling, with safety guards on destructive operations.
      108
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets local AI agents drive an Omarchy desktop by exposing its command registry and shell IPC targets over MCP, enabling command search, execution, and desktop state control.
      12
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect, control, and automate Arch Linux/CachyOS and the Niri Desktop Environment through natural language, featuring tools for window management, system administration, package queries, and hardware control.
      35
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to generate beautiful Hyprland and Waybar configurations with embedded wiki references and theme templates.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to automate Hyprland desktop environments through screenshots, mouse/keyboard input, window management, workspaces, clipboard, app launching, and OCR.
      27
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action on themes: install, preview, remove, cycle background, list, and set. There is no overlap or ambiguity; an agent can clearly distinguish when to use each.

    Naming Consistency4/5

    All tools use snake_case with a consistent 'omarchy_' prefix. Most follow a verb_noun pattern (e.g., install_theme, preview_theme), though 'theme_bg_next' and 'theme_list' slightly deviate from the order. Overall, the pattern is clear and predictable.

    Tool Count5/5

    Six tools is well-scoped for a theme management server. Each tool serves a necessary function without redundancy, covering installation, removal, listing, setting, previewing, and background cycling.

    Completeness4/5

    The tool set covers the main lifecycle of themes: install, remove, list, set, preview, and background control. A minor gap is the lack of an explicit 'get current theme' tool, but that may be inferred from the set action. Overall, it is sufficiently complete for typical theme management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues