Hypruse vs Windows Computer Use MCP
A side-by-side look at the Hypruse and Windows Computer Use MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hypruse for os automation work as a local process; choose Windows Computer Use MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hypruse when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HYPRUSE_CLIPBOARD. - You want tools like
desktop, screenshot, zoom.
Choose Windows Computer Use MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
screenshot, zoom, mouse_move.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 56/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HYPRUSE_CLIPBOARD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 36 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 18 |
| Full listing | View Hypruse | View Windows Computer Use MCP |
Tools & capabilities
Hypruse tools 15
desktopOne-call semantic snapshot: monitors, workspaces, windows (address/class/title/geometry), active window, cursor, and layer surfaces (launchers, bars, notification popups) with a best-effort kind and geometry. A listed layer is one the compositor tracks, not one you can see: transparent and dormant…screenshotFocused monitor, one window by address (with grim 1.5+ on Hyprland 0.54+, even hidden or covered; metadata `visible` says whether the compositor draws it, `source` whether the pixels are the window's own or a screen crop, and a hidden capture may be stale), or `x,y,WxH` region; returns image + coor…zoomNative-resolution re-capture around an estimated point (optionally clamped to a window): the precision step before clicking small controls, same metadata contractuiRead a window's accessibility tree (AT-SPI, GTK/Qt apps that expose one) and return clickable elements by name with exact global coordinates, no screenshot; reports current values too (typed text, slider position, checkbox state); falls back to vision when an app exposes nothingmarksSet-of-Marks capture: the window screenshot with every accessible control drawn as a numbered mark, plus a JSON legend (role, name, current value, exact click point per number); needs ImageMagick for the drawing, degrades to the legend alone without itclick_uiClick a control by accessible NAME or by a `marks` number in one call: the coordinate comes from the tree, the click goes through the real pointer (visible, same safety guarantees); an ambiguous name returns the candidates instead of guessingpointermove / click / drag / scroll (discrete wheel notches) in global coordinateskeyboardType literal text (unicode-safe) or press app-level combos (`ctrl+shift+t`, `esc`, `F5`); optional `window` address focuses the target first so keystrokes land in the right app. Compositor binds (`super+...`) go through `use_bind`, not herehyprSwitch workspace, focus/move/close windows, fullscreen, floating (pure IPC, milliseconds; `close_window` also waits up to 1s for the destroy event, so its result and `then=` observation reflect the close instead of racing it)launchStart an app (optionally silent on another workspace), block on its actual `openwindow` event, return its address; detects single-instance apps (browsers) whose window ignores exec rules and moves it to the requested workspacebindsThe user's own keybinds, decoded (`SUPER+Q`, action, description); the agent runs one with `use_binduse_bindExecute a keybind by combo (`SUPER+F`), running its bound action, so the agent drives the owner's own launchers and shortcuts. Not available for binds in a Lua `hyprland.lua`: those are anonymous closures Hyprland exposes no way to call, so `binds` shows them as action `lua` and `use_bind` says so…- +3 more on the listing page
Windows Computer Use MCP tools 18
screenshotTake a screenshot of the current screenzoomTake a screenshot of a specific regionmouse_moveMove the mouse cursor to coordinatesleft_clickLeft-click at coordinates or current positionright_clickRight-click at coordinatesdouble_clickDouble-click at coordinatesleft_click_dragClick and drag from one point to anotherscrollScroll the mouse wheeltypeType a string of textkeyPress a key combination (e.g. `ctrl+c`, `alt+f4`)hold_keyHold a key for a durationcursor_positionGet current cursor position- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hypruse
{
"mcpServers": {
"hypruse": {
"command": "uvx",
"args": [
"hypruse"
],
"env": {
"HYPRUSE_CLIPBOARD": "YOUR_HYPRUSE_CLIPBOARD_HERE"
}
}
}
}
Windows Computer Use MCP
{
"mcpServers": {
"windows-computer-use-mcp": {
"command": "npx",
"args": [
"-y",
"windows-computer-use-mcp"
]
}
}
}
Frequently asked questions
Hypruse is categorized under OS Automation and uses a local stdio subprocess. Windows Computer Use MCP belongs to OS Automation and uses a local stdio subprocess. Pick Hypruse for os automation work and Windows Computer Use MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Hypruse has no declared pricing — check the project's own site. Windows Computer Use MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hypruse and windows-computer-use-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hypruse has a quality signal of 56/100 (Good) with 0 views, 0 installs and 36 GitHub stars. Windows Computer Use MCP has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.