← home · dashboard · llms.txt

Loopback relay — docs

Remote-control harness hub · v0.5.5 · 1 agent(s) online0 controller(s)

Three parts over WebSocket: this relay routes messages; an agent runs on a target machine (a Windows kiosk) and dials in; an MCP bridge on the operator's machine lists agents, attaches to one, and drives it. For an LLM-readable version of this page, see /llms.txt.

Relay endpoint

WebSocket URL for agents and controllers: wss://loopback.elevated.app
Health check: /healthz
Auth: a shared token, provided by the relay operator (not shown on this public page).

1. Run an agent on the target machine

# Download and run on the kiosk (PowerShell):
Invoke-WebRequest https://loopback.elevated.app/download/loopback-agent-windows-x64.exe -OutFile loopback-agent.exe
.\loopback-agent.exe --relay wss://loopback.elevated.app --token  --root C:\kiosk-app

Replace <TOKEN> with the relay token. The agent gives whoever holds the token full read/write, shell, screenshot and input control of that machine, over TLS.

2. Connect the MCP bridge (operator machine)

Download the matching loopback-mcp binary below, then register it as an MCP server:

{
  "mcpServers": {
    "loopback": {
      "command": "loopback-mcp",
      "env": {
        "LOOPBACK_RELAY_URL": "wss://loopback.elevated.app",
        "LOOPBACK_TOKEN": ""
      }
    }
  }
}

Or with Claude Code: claude mcp add loopback -e LOOPBACK_RELAY_URL=wss://loopback.elevated.app -e LOOPBACK_TOKEN=<TOKEN> -- loopback-mcp

Downloads

Tools

Files: read, write, edit, list, stat, mkdir, remove, move, glob, grep. Shell: run (bash/sh/zsh/cmd/powershell/pwsh). Debugging: screenshot (PNG/JPEG), click, type, key (drive the UI), download (stream large logs).