Ansight Studio is the desktop app that owns pairing, saved session inspection, and the local MCP surface.

What Studio Does

Studio is responsible for:

  • tracking known apps and optional linked codebases
  • issuing signed, expiring pairing configs
  • generating QR payloads for device pairing
  • receiving live sessions from paired apps
  • browsing logs, telemetry, screenshots, and device state
  • exporting portable session archives
  • exposing Studio and live-app capabilities over the local MCP bridge

Install and Launch

Run Studio on a trusted desktop machine. Keep it on the same local network as the device or simulator you want to pair.

When Studio is running, the MCP bridge is available locally at:

http://127.0.0.1:45125/mcp/

Register an App

Before pairing, create an app entry in Studio.

The app workspace lets you store:

  • app name
  • app identifier
  • optional codebase folder
  • optional app icon

Linking the codebase is optional for pairing, but useful when you want Studio and agents to keep the runtime session tied to a known app entry.

Issue Pairing Configs

Studio can issue multiple pairing configs for an app.

When you issue a config, Studio records:

  • app id and app name
  • a one-time token
  • issued and expiry timestamps
  • the host public key and fingerprint
  • the challenge public key used during first-pair proof

Accepted duration inputs include values such as:

  • 30m
  • 12h
  • 7d
  • 1mo

Studio keeps the config in its local cache and writes a JSON file you can hand to the app or embed into a development build.

Show a QR Pairing Payload

After you select a pairing config and host address, Studio can generate a QR payload.

That payload combines:

  • the selected pairing config
  • a discovery hint for the chosen host address
  • optional host metadata such as host name and Wi-Fi name

This is the easiest way to pair a physical device without moving JSON files around manually.

Capture and Inspect Sessions

When a paired app connects, Studio stores session data such as:

  • logs
  • telemetry channels and samples
  • screenshots and session images
  • device and app metadata
  • saved analyses and flow charts

The dashboard lets you:

  • filter sessions by app
  • inspect a session timeline
  • view logs and telemetry
  • inspect device properties
  • review screenshots
  • open saved analyses
  • export the session as an archive

Use Studio as an MCP Bridge

Studio exposes host-owned MCP tools and can proxy live app-defined tools into a paired session.

In practice that means an agent can:

  • list apps, devices, and sessions
  • inspect captured logs and telemetry
  • query the live tool catalog for a paired app
  • call a remote app tool through Studio

Studio keeps this bridge local to the desktop. It is not a cloud relay.

  1. Register the app in Studio.
  2. Issue a short-lived pairing config.
  3. Show a QR payload or hand the JSON file to the app team.
  4. Pair the app from a debug or internal development build.
  5. Reproduce a problem and inspect the live or saved session in Studio.
  6. Connect an MCP-capable agent to the local bridge when you want AI-assisted analysis.