Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hypruse

No user-submitted related servers found.

    Related Servers

    • hyprland-mcp

      alderban107
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for Hyprland desktop automation that allows AI assistants to see the screen, control mouse and keyboard, and manage windows using native Wayland tools. It integrates OCR for text-based interaction and supports complex multi-monitor setups with pixel-accurate coordinate mapping.
      27
      5
      MIT

    • hyprcu

      angusforbes
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control Hyprland desktops via MCP, including pointer/keyboard input, screenshots, launching apps, and natural-language window targeting using a local decision model.
      14
      1
      MIT

    • kwin-mcp

      Samthesurf
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that controls native Wayland windows on KDE Plasma from an AI agent, enabling window listing, screenshots, clicks, typing, and more.
      MIT

    • hypruse

      XLRC888
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling Hyprland Wayland compositor: screen capture, mouse/keyboard injection, and automation via native Hyprland IPC and wlr protocols.
      MIT

    • dual-wield-mcp

      SpiritualMachines
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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

    • ghost-desktop

      ferdousbhai
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets agents observe and control an Omarchy or Hyprland desktop: list monitors, windows, workspaces, and accessibility controls, capture screenshots, then move the pointer, type text, send shortcuts, and manage windows and workspaces. It works over stdio with any MCP client, guarding actions with session-lock and single-driver checks while treating on-screen content as untrusted data.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool serves a clearly distinct function: desktop provides semantic state, screenshot/zoom capture visual data, marks/ui expose accessibility info, keyboard/pointer/click_ui handle input, hypr/launch/use_bind execute actions, wait_for listens for events, and sequence orchestrates multi-step workflows. No two tools have overlapping purposes that could cause misselection; even similar tools like marks and ui differ in output format and use case.

    Naming Consistency4/5

    All names are lowercase and descriptive, with compound names consistently using underscores (wait_for, click_ui, use_bind). However, the set mixes nouns (desktop, marks, pointer, screenshot) with verbs (launch, wait_for, click_ui), so there's no strict verb_noun pattern, but the inconsistency is minor and doesn't hinder understanding.

    Tool Count5/5

    14 tools is well-scoped for a desktop automation server, covering state inspection, input, action execution, event waiting, and sequencing. Each tool is necessary and non-redundant, and the count is within the ideal 3-15 range.

    Completeness5/5

    The tool surface is comprehensive for desktop automation: it provides state discovery (desktop, ui, binds), input (keyboard, pointer, click_ui), action execution (hypr, launch, use_bind), observation (screenshot, zoom, marks), event handling (wait_for), and multi-step orchestration (sequence). No obvious gaps exist for typical workflows; even edge cases like authentication dialogs are addressed via allow_auth flags.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources