Connect via MCP

Glasswarp ships a remote MCP server so MCP-enabled assistants and IDEs get eyes and hands on a paired Windows PC without writing project code. You bring the brain (the model and the prompts); Glasswarp provides vision, native input, and a safe session. Marketing overview: glasswarp.com/mcp.

MCP sessions are ordinary metered Platform API sessions — same concurrency, active minutes, consent, indicator, kill switch, and audit as REST / SDK.

Prerequisites

Install and pair a Windows host

Install the host, pair the rig, and turn on API access for that rig in the console.

Create an API key

Console → API Keys. Same gw_* key authenticates REST and MCP. Copy it once when created.

Host online

list_rigs only marks a rig USABLE when it is online and API-enabled. Start the Windows host agent before asking the assistant to act.

Endpoint


URL	`https://mcp.glasswarp.com/mcp`
Transport	Streamable HTTP
Auth	`Authorization: Bearer <glasswarp_api_key>`
Platform API	`https://signal.glasswarp.com` (same sessions / metering)

Client config

Use your real API key from the console — not placeholder text.

Cursor (recommended)

Current Cursor builds often fail remote Streamable HTTP with fetch failed. Bridge with mcp-remote over stdio, and use an absolute npx path for your OS (bare npx often breaks inside Cursor.app).

macOS (Apple Silicon)

{
  "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"
      }
    }
  }
}

macOS (Intel)

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

Windows

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

If Cursor cannot find npx, use the full path from Node.js (often C:\\Program Files\\nodejs\\npx.cmd).

Linux

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

If npx lives elsewhere (nvm, fnm), point command at that absolute path.

Toggle the server off/on after saving.

Direct remote URL

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

After reload, the client should list tools such as list_rigs, start_session, observe, click_target, type_text, send_actions, launch_app, list_demos, get_demo, get_live_view_url, and end_session.

First session

Ask your assistant:

Open Notepad on my PC and type hello from MCP.

Typical tool flow: list_rigs → start_session → observe → click / type → observe → end_session Always end the session when finished. Idle sessions auto-end after about 15 minutes.

What to expect from your assistant

On connect, the server gives every MCP client behavioral guidance. In practice: your assistant handles quick tasks directly in chat — look at the screen, click, type. For longer multi-step work in a code-capable client, it will offer to write a small SDK agent that runs the loop at full speed instead of one chat turn per action — your choice either way. Chat-only clients simply keep working through MCP tools. Details and the pre-built demo catalog: Ways to run agents.

Live View (human in the loop)

get_live_view_url returns a console deep link. The rig owner must be signed into Glasswarp to watch at ~60fps and intervene. API keys alone cannot open the console player — that preserves owner consent. See Live View.

Tools (v1)

Tool	Role
`list_rigs`	List paired rigs
`start_session` / `end_session`	Session lifecycle
`observe`	Screenshot + targets (image + text)
`click_target` / `click_xy`	Mouse (prefer targets; `click_xy` uses native capture coords)
`type_text` / `send_keys` / `drag` / `scroll`	Keyboard and pointer
`launch_app`	Start an app on the host (`args` optional)
`list_demos` / `get_demo`	Pre-built demo catalog (install + command; they do not run the demos)
`get_live_view_url`	Owner console Live View URL
`get_session_status`	Session status

Prompts: best_practices, demo_mona_lisa, demo_minesweeper

Troubleshooting

Cursor: ENOENT / bare npx fails

Bare npx is often broken in Cursor’s spawn environment. Use the absolute npx path for your platform from the Cursor section above (Apple Silicon Homebrew, Intel Homebrew, Windows Node.js, or Linux).

fetch failed / ByteString / ellipsis in header

Do not paste truncated keys with …. Use the full gw_live_sk_… value from the console. Prefer the stdio mcp-remote bridge on Cursor.

list_rigs works but rig is not usable

Online=false means the Windows host agent is not connected. Start GlasswarpHost on that PC; keep API access enabled in Console → Rigs.

Platform API hostname does not resolve

If signal.glasswarp.com (or your configured API base URL) fails to resolve on your machine, flush your local DNS cache or try a public resolver (for example 1.1.1.1 or 8.8.8.8). The MCP server reaches the Platform API from its own network — local DNS only affects tools you run on your machine.

Building a product instead?

Use the Python SDK and Setup for Agents. MCP is for assistants out of the box; the SDK is for products you ship.

Get started

Setup

Concepts

Guides

Examples

Help

Prerequisites

Endpoint

Client config

Cursor (recommended)

Direct remote URL

First session

What to expect from your assistant

Live View (human in the loop)

Tools (v1)

Troubleshooting

Building a product instead?

​Prerequisites

​Endpoint

​Client config

​Cursor (recommended)

​Direct remote URL

​First session

​What to expect from your assistant

​Live View (human in the loop)

​Tools (v1)

​Troubleshooting

​Building a product instead?

Prerequisites

Endpoint

Client config

Cursor (recommended)

Direct remote URL

First session

What to expect from your assistant

Live View (human in the loop)

Tools (v1)

Troubleshooting

Building a product instead?