Glasswarp vs Open Compute (computer Use)
A side-by-side look at the Glasswarp and Open Compute (computer Use) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Glasswarp for os automation work as a local process; choose Open Compute (computer Use) 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 Glasswarp when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GLASSWARP_API_KEY. - You want tools like
demos.list, demos.get, rigs.list.
Choose Open Compute (computer Use) when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
capture, do, tree.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 57/100 · Good | 56/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 | GLASSWARP_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 16 |
| Full listing | View Glasswarp | View Open Compute (computer Use) |
Tools & capabilities
Glasswarp tools 16
demos.listList showcase run contracts (id, title, install, command). Read-only catalog — does NOT start a session, touch a rig, or run solvers. Use when the user asks for Minesweeper/Mona Lisa/Paint demos or you need the glasswarp-demo command. Prefer demos.get for one full card. For ad-hoc UI work use rigs.list → session.start → screen.observe instead.demos.getReturn one showcase run contract (install, command, needs, framing). Does NOT execute the demo or control a PC. Call after demos.list when you know the demo_id. If the client can run shell, offer the command; if chat-only, show the card. Do not replace this with a slow MCP click loop for solver demos.rigs.listList Windows machines (rigs) paired to this API key: id, name, online, api_access_enabled, and USABLE flag. Read-only — does not start a session. Call first before start_session. A rig is USABLE only when online AND the owner enabled API access. If none are USABLE, tell the user to install the host agent, pair in Console → Rigs, and enable API access — never ask for OS passwords.session.startStart a metered desktop session on a USABLE rig from rigs.list. Side effects: begins wall-clock billing, shows an on-screen “API session active” indicator, enables observe/input until session.end. Idle sessions auto-end after ~15 minutes. Always call session.end when done or abandoning. Do not call if no USABLE rig exists. Returns session_id and Live View URL (owner console login required).session.endEnd an active session. Side effects: stops billing, runs host safety_restore, closes apps launched via app.launch. Always call when finished or abandoning — do not leave sessions open. Safe to call once; further observe/input on that session_id will fail.screen.observeRead the current screen: UIA targets (numbered ids + native coords) and a text summary. Does not move mouse/keyboard. Default image=false (no JPEG) for speed; set image=true only when you must judge pixels visually (then max_width≈960, quality≈60). If changed=false, JPEG is omitted even when requested — do not re-analyze; wait or act differently. If dirty is null, assume changed. Prefer input.send_actions for multi-step UI; observe after meaningful steps, not after every click. Target ids are valid only until the next UI change.input.click_targetLeft/right/middle-click a UIA target by id from the latest screen.observe (uses native center coords). Prefer over input.click_xy. Side effect: real mouse click on the remote Windows desktop. Do not reuse target_id after the screen may have changed — re-observe first. For click→type→keys sequences, use input.send_actions (one turn) instead of chaining this tool.input.click_xyClick at native screen coordinates (0…native_width-1, 0…native_height-1 from screen.observe). Last resort when no suitable UIA target exists — prefer input.click_target. Never use JPEG/downscaled pixel coords. Side effect: real mouse click on the remote desktop.input.type_textType a Unicode string into the currently focused control via native input. Does not click first — focus the field (input.click_target / input.send_actions) before calling. Side effect: keystrokes on the remote desktop. For form fills (click → type → tab/enter), prefer input.send_actions in one call.input.send_keysSend a key or chord to the focused window (e.g. enter, tab, ctrl+s, alt+f4, win). Side effect: real key events on the remote desktop. Prefer bundling into input.send_actions when the shortcut follows a click/type in the same planned sequence. Use input.type_text for literal strings, not this tool.input.dragPress-move-release mouse drag in native capture coordinates. Use for drawing, sliders, selection boxes, and drag-and-drop. Side effect: mouse_down → moves → mouse_up on the remote desktop. Prefer input.send_actions if the drag is one step in a longer predictable sequence.input.scrollMove the cursor to native (x,y) then apply a vertical mouse-wheel delta. Side effect: scroll on whatever is under that point. Negative delta scrolls toward the bottom of the page. Prefer input.send_actions when scroll is part of a multi-step sequence. Re-observe after scrolling lists/pages before clicking targets.- +4 more on the listing page
Open Compute (computer Use) tools 16
captureReturn one-shot observation metadata plus an image (optionally one exact window).doExecute a safety-gated action; coordinates require `observation_id` + issued window descriptor/token.treeReturn UIA elements and a one-shot observation ID for their coordinates.click_nameExact-first, ambiguity-safe click in a required issued window, with score/alternatives.invokeExact-first, click-free UIA activation in a required issued window.list_windowsList stable window/process IDs, exact titles, issued tokens, rects and centers.get_screen_sizeVirtual-desktop geometry + per-monitor breakdown (read-only).watch_dirWatch directories for file-system changes.push_statusFeed-manager status (read-only).rec_replayReplay a `.clirec` macro (needs the optional `clirec` package).signal_showShow a configurable pre-action color/text countdown, then the mode-colored overlay, with owner/session lease and bounded TTL.signal_hideHide the signal overlay.- +4 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.
Glasswarp
{
"mcpServers": {
"glasswarp": {
"command": "npx",
"args": [
"-y",
"@glasswarp/mcp"
],
"env": {
"GLASSWARP_API_KEY": "YOUR_GLASSWARP_API_KEY_HERE"
}
}
}
}
Open Compute (computer Use)
{
"mcpServers": {
"open-compute-computer-use": {
"command": "npx",
"args": [
"-y",
"open-compute-mcp"
]
}
}
}
Frequently asked questions
Glasswarp is categorized under OS Automation and uses a local stdio subprocess. Open Compute (computer Use) belongs to OS Automation and uses a local stdio subprocess. Pick Glasswarp for os automation work and Open Compute (computer Use) 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.
Glasswarp has no declared pricing — check the project's own site. Open Compute (computer Use) 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 glasswarp and open-compute-computer-use as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Glasswarp has a quality signal of 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Open Compute (computer Use) has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.