Ibara vs Hypruse
A side-by-side look at the Ibara and Hypruse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
IbaraOS AutomationLet MCP agents use the desktop, browser and apps on Omarchy computers you own. ibara connects over your Tailscale network, with live viewing and human control handoff. Install the signed native packages first using https://ibara.app/docs/install, then run ibara mcp for stdio MCP. Requires Omarchy 4 and Tailscale; it is not an npm package or public hosted MCP endpoint.52GoodAuth: otherVerdict: choose Ibara for os automation work; choose Hypruse 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?
IChoose Ibara when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: other.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Ibara | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 52/100 · Good | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | HYPRUSE_CLIPBOARD |
| Verified owner | Community listing | Community listing |
Tools & capabilities
Ibara tools
No tool names declared yet. Check the project README from the listing page.
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, exact window crop by address, or `x,y,WxH` region; returns image + coordinate-mapping metadata; fast JPEG by default (`lossless=true` for PNG); `stable=true` waits for the frame to settlezoomNative-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 here
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.
Ibara
No confirmed install command for Ibara yet — follow the setup steps linked from its listing page rather than a guessed package name.
Hypruse
{
"mcpServers": {
"hypruse": {
"command": "uvx",
"args": [
"hypruse"
],
"env": {
"HYPRUSE_CLIPBOARD": "YOUR_HYPRUSE_CLIPBOARD_HERE"
}
}
}
}
Frequently asked questions
Ibara is categorized under OS Automation and uses an install path we have not confirmed yet. Hypruse belongs to OS Automation and uses a local stdio subprocess. Pick Ibara for os automation work and Hypruse 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. Ibara has no confirmed install command yet — follow its own setup instructions.
Ibara is listed as free. Auth: other. Hypruse 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 ibara and hypruse as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ibara has a quality signal of 52/100 (Good) with 2 views, 0 installs and 8 GitHub stars. Hypruse has 56/100 (Good) with 0 views, 0 installs and 33 GitHub stars.