Loopback · llms.txt

# Connect Claude Code to Loopback

Loopback is a remote MCP server that lets Claude Code inspect and operate Elevation kiosks.
Nothing is installed: Claude Code connects over HTTP and the engineer signs in with their
Elevation Microsoft account (Entra ID).

These steps are written for an AI assistant setting this up on the engineer's machine.

## 1. Prerequisite

The engineer's Microsoft account must hold the Loopback Operator app role on the Loopback app
(an Entra administrator assigns it). Without it the sign-in succeeds but the server answers 403.

## 2. Add the server

    claude mcp add --transport http --client-id ef0df5fa-d56e-457a-bcf5-293f3004fe02 --callback-port 33418 loopback https://loopback-qa.elevated.app/mcp

Add `--scope user` to make it available in every project. The OAuth scopes are
`https://loopback-qa.elevated.app/mcp/Loopback.Operate offline_access`; Claude Code learns them from the server.

## 3. Sign in

Start Claude Code, run `/mcp`, select `loopback` and choose Authenticate. A browser opens the
Microsoft sign-in; afterwards it returns to http://localhost:33418/callback. Port 33418 must be free.
`claude mcp list` then shows loopback as connected.

## 4. Use it

Ask Claude Code to list the remote hosts (remote_list_hosts), pick one (remote_use) and work
with the remote_* tools. kb_search / kb_read open the team knowledge base; kb_propose suggests
a new article for review.

## Kiosks

A kiosk appears once Loopback is enabled for it in AirOps Admin > Remote Support (Kiosk access).
AirOps adds the Loopback module to the kiosk's launcher; it runs in memory, writes no files,
and streams its log to the relay (remote_logs). Disabling it there removes it again.