Other · Local MCP server
hypruse
Computer use for Hyprland: semantic desktop state over IPC, plus vision and native input.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.IlyasKhallouki/hypruse- Version
- 0.11.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- IlyasKhallouki (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/IlyasKhallouki) · how
- Website
- github.com/IlyasKhallouki/hypruse#readme
- Repository
- github.com/IlyasKhallouki/hypruse
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | hypruse | 0.11.0 | stdio |
How to connect hypruse
hypruse runs locally from a Python package published to PyPI: hypruse version 0.11.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx hypruse. It reads these environment variables: HYPRUSE_SCREENSHOT_MODE, HYPRUSE_READONLY, HYPRUSE_CONFINE, HYPRUSE_AUTH_GUARD, HYPRUSE_STRICT, HYPRUSE_MARK, HYPRUSE_CLIPBOARD, HYPRUSE_JOURNAL, HYPRUSE_JOURNAL_MAX_BYTES, HYPRUSE_JOURNAL_TEXT and HYPRUSE_DRYRUN; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"hypruse": {
"command": "uvx",
"args": [
"hypruse"
],
"env": {
"HYPRUSE_SCREENSHOT_MODE": "<value>",
"HYPRUSE_READONLY": "<value>",
"HYPRUSE_CONFINE": "<value>",
"HYPRUSE_AUTH_GUARD": "<value>",
"HYPRUSE_STRICT": "<value>",
"HYPRUSE_MARK": "<value>",
"HYPRUSE_CLIPBOARD": "<value>",
"HYPRUSE_JOURNAL": "<value>",
"HYPRUSE_JOURNAL_MAX_BYTES": "<value>",
"HYPRUSE_JOURNAL_TEXT": "<value>",
"HYPRUSE_DRYRUN": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Hypertool MCPDynamically expose tools from proxied servers based on an Agent Persona. | Local · stdio |
| HypertuneEvaluate and inspect your Hypertune feature flags from your AI assistant. | Remote · HTTPLive check: ✓ handshake |
| HyperXosist-Agent Remote MCPX feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs. | Remote · HTTPLive check: ✓ handshake |
| Hypr Cua MCPHyprland/Wayland computer-use MCP: grim screenshots + uinput click/type + hyprctl targeting. | Local · stdio |
| HytheHYTHE - coordination bus + shared truth for AI agent fleets - self-hosted MCP server + stdio bridge. | Local · stdio |
| I Ching MCP Server by RoxyAPII Ching hexagram casts, 64 hexagram meanings and changing lines for AI agents. | Remote · HTTPLive check: ✓ handshake |
| I18n Codelens MCPInspect, audit and safely edit i18n locale JSON files from AI agents. | Local · stdio |
| i18n-agentAI-powered translation for 48 languages with context-aware quality. | Remote & Local · HTTP, stdioLive check: sign-in required |