← Glasswarp

Connect your assistant — eyes and hands on Windows via MCP

Connect Glasswarp to any MCP-enabled assistant or IDE and give it eyes and hands on a Windows PC you or your client already own — no integration code. Built for automators driving no-API desktop apps as well as agent builders. You bring the brain; we provide vision, native input, and a safe session.

Prerequisite (owner consent)

The machine owner must install the Windows host, pair the rig, and enable API access. This step cannot be skipped and never requires sharing Windows passwords.

1. Download the host agent
2. Pair the PC
3. Enable API access in the console
4. Create an API key

Remote MCP server

Endpoint: https://mcp.glasswarp.com/mcp (Streamable HTTP).
Auth: Authorization: Bearer <glasswarp_api_key> (use your real console key — not placeholder text).

Add to Cursor — then set GLASSWARP_API_KEY to your console key.

Cursor (recommended if you see fetch failed) — use an absolute npx path for your OS:

macOS Apple Silicon — /opt/homebrew/bin/npx

macOS Intel — /usr/local/bin/npx

Windows — npx or full npx.cmd

Linux — typically /usr/bin/npx

{
  "mcpServers": {
    "glasswarp": {
      "command": "/opt/homebrew/bin/npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.glasswarp.com/mcp",
        "--header",
        "Authorization:${GLASSWARP_AUTH}"
      ],
      "env": {
        "PATH": "/opt/homebrew/bin:/usr/bin:/bin",
        "GLASSWARP_AUTH": "Bearer gw_live_sk_REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

Swap command / PATH for your platform. Full configs: docs → Connect via MCP.

Direct remote URL:

{
  "mcpServers": {
    "glasswarp": {
      "url": "https://mcp.glasswarp.com/mcp",
      "headers": {
        "Authorization": "Bearer gw_live_sk_REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

What to expect from your assistant

Quick tasks happen directly in chat — your assistant looks at the screen, clicks, and types. For longer multi-step work in a code-capable client, it will offer to write a small SDK agent (or run a pre-built glasswarp-demo) that loops at full speed instead of one chat turn per action — your choice either way. Guide: Ways to run agents.

Your first session

Ask your assistant: “Open Notepad on my PC and type hello from MCP.”

Typical tool flow: rigs.list → session.start → screen.observe → click/type → observe → session.end. Always end the session when finished; idle sessions auto-end after ~15 minutes.

Billing

MCP sessions are ordinary metered sessions — same concurrency and active minutes as the REST API. See pricing.

Listed on Smithery.