Glasswarp vs Oswright
A side-by-side look at the Glasswarp and Oswright 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 Oswright 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 Oswright when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
screenshot, get_screen_info, find_text_on_screen.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 57/100 · Good | 59/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 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 43 |
| Full listing | View Glasswarp | View Oswright |
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
Oswright tools 43
screenshotTake a screenshot of the screen or a region. Returns the image as native MCP image content. Optionally saves to a file path. Args: save_path: Optional file path to save the screenshot. region_left: Left coordinate for a sub-region capture. region_top: Top coordinate for a sub-region capture. region_width: Width of the sub-region. region_height: Height of the sub-region. monitor: Monitor index (0 = all monitors, 1 = primary, etc.).get_screen_infoGet screen dimensions and monitor count. Args: monitor: Monitor index (0 = all monitors combined).find_text_on_screenFind all occurrences of text on screen using OCR. Returns a list of matches with coordinates and confidence. Coordinates are absolute screen coordinates, ready to pass straight to mouse_click. Args: text: The text to search for on screen. exact: If True, requires exact match. If False, substring match. region_left: Optional left bound to restrict search area. region_top: Optional top bound to restrict search area. region_width: Optional width to restrict search area. region_height: Optional height to restrict search area. monitor: Monitor index.read_screen_textRead ALL visible text on the screen using OCR. Returns every detected text element with its position, in absolute screen coordinates that are ready to click. Args: region_left: Optional left bound to restrict OCR area. region_top: Optional top bound to restrict OCR area. region_width: Optional width to restrict OCR area. region_height: Optional height to restrict OCR area. monitor: Monitor index.find_image_on_screenFind all occurrences of a template image on screen. Coordinates are absolute screen coordinates, ready to pass to mouse_click. Args: template_path: Absolute path to the template image file to find. threshold: Minimum match confidence (0.0-1.0, default 0.8). monitor: Monitor index.mouse_clickClick the mouse at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. If not provided, clicks at current position. y: Y screen coordinate. If not provided, clicks at current position. button: Mouse button - 'left', 'right', or 'middle'. clicks: Number of clicks (2 for double-click).mouse_double_clickDouble-click at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. y: Y screen coordinate.mouse_moveMove the mouse cursor to screen coordinates. Args: x: X screen coordinate. y: Y screen coordinate.mouse_scrollScroll the mouse wheel. Returns action result and a screenshot of current screen state. Args: amount: Scroll amount. Positive = up, negative = down. x: Optional X coordinate to scroll at. y: Optional Y coordinate to scroll at.mouse_dragDrag from one point to another. Returns action result and a screenshot of current screen state. Args: start_x: Starting X coordinate. start_y: Starting Y coordinate. end_x: Ending X coordinate. end_y: Ending Y coordinate. button: Mouse button to hold ('left' or 'right'). duration: Duration of the drag in seconds.get_mouse_positionGet the current mouse cursor position.type_textType text using the keyboard (character by character). Returns action result and a screenshot of current screen state. Args: text: The text to type. delay: Delay in seconds between each character.- +31 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"
}
}
}
}
Oswright
{
"mcpServers": {
"oswright": {
"command": "uvx",
"args": [
"oswright"
]
}
}
}
Frequently asked questions
Glasswarp is categorized under OS Automation and uses a local stdio subprocess. Oswright belongs to OS Automation and uses a local stdio subprocess. Pick Glasswarp for os automation work and Oswright 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. Oswright 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 oswright 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. Oswright has 59/100 (Good) with 2 views, 0 installs and 4 GitHub stars.