Glasswarp MCP Server

by glasswarp Your server? Claim it

answering

Glasswarp is answering right now. Last checked 8 min ago. It exposes 16 tools. Last commit 1 Aug 2026.

Eyes and hands on real Windows PCs — observe, click, type via Glasswarp API.

Uptime history 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

362 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

What the code does

We read the source, 3 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command packages/mcp/bin/glasswarp-mcp.js:76

const child = spawn(process.execPath, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-server --transport http https://mcp.glasswarp.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.glasswarp.com/mcp

~/.codex/config.toml

[mcp_servers.mcp-server]
url = "https://mcp.glasswarp.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.glasswarp.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp-server": {
      "type": "http",
      "url": "https://mcp.glasswarp.com/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

input

input.click_target

Left/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_xy

Click 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.drag

Press-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.scroll

Move 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.

input.send_actions

PREFERRED multi-step tool: run 1–10 predictable UI actions in one call (input.click_target, input.click_xy, input.type_text, input.send_keys, input.drag, input.scroll). Side effects: all actions execute on the remote desktop; fails fast before sending if any action is invalid. observe_after defaults true (verification observe: text+targets; set observe_image=true for JPEG). Do not batch across unpredictable waits (page loads, installers, modals) — single-step those. Prefer this over chaining solo click/type/keys tools.

input.send_keys

Send 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.type_text

Type 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.

session

session.end

End 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.

session.live_view

Return the console Live View URL (≈60fps) for the rig owner to watch and intervene. Read-only for the agent — does not grant the API key console access. Offer on long or sensitive tasks. Owner must be signed into Glasswarp; API keys alone cannot open the player.

session.start

Start 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.status

Fetch session metadata: status, host, mode, created_at, action_count, billed_minutes. Read-only — no input side effects. Use to tell the user about metered time or confirm the session is still active before more actions.

demos

demos.get

Return 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.

demos.list

List 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.

app

app.launch

Launch an executable on the remote Windows rig (name on PATH or absolute path), optional args. Side effects: starts a process; Glasswarp tracks it and closes it on session.end. Use for notepad.exe, mspaint.exe, chrome with URL args, etc. Wait/re-observe after launch before clicking — do not assume the window is focused immediately.

rigs

rigs.list

List 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.

screen

screen.observe

Read 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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.glasswarp.com/mcp	streamable-http	answering	273 ms	8 min ago

Alternatives to Glasswarp

same job, measured the same way

HaloPSA

by wyre-technology

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only

HaloPSA

by wyre-ai

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only

Pixelcheck

by xcodethink

Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic.

65 installs/wk local only

Oya Browser

by oyadotai

Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.

32 tools answering

Clipboard MCP Server

by cyanheads

Read, write, and inspect the system clipboard on macOS, Linux (X11/Wayland), and Windows via MCP.

244 installs/wk local only

Outlook Classic

by jli-software

Mail, calendar and contacts of classic Outlook on Windows via COM. Single EXE, no Graph app.

local only

Text to Speech

by engr-faizanali

Reads text aloud locally on Windows, macOS, and Linux. No API key, account, or cloud service.

146 installs/wk local only

Hetzner Cloud (unofficial)

by mguttmann

Unofficial MCP server for the Hetzner Cloud API: one typed tool per operation, read and write.

74 installs/wk local only

Glasswarp — questions

Answers built from our own checks of this server.

What can Glasswarp do?

It exposes 16 tools, read directly from the server on our last check. Among them: app.launch, demos.get, demos.list, input.click_target, input.click_xy, input.drag and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Glasswarp mostly used for?

Its tools cluster around input, session and demos. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Glasswarp working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 362 ms. The bar chart above shows every period we have measured.

How do I connect Glasswarp?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Glasswarp need an API key?

No. Glasswarp completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Glasswarp?

It answers our handshake in 362 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Glasswarp open source?

The code is open source: it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.glasswarp.com, which runs on its operator's own terms.