Ansight Studio

Use Ansight Studio as the desktop control plane for app setup, pairing, session capture, replay, annotations, telemetry review, exports, and local MCP access.

Ansight Studio is the desktop app that owns app setup, pairing, live session intake, saved session review, annotations, telemetry review, exports, and the local MCP bridge used by AI agents.

Ansight Studio runs on a trusted developer machine. Product teams use it directly to capture and review app behavior, while agents use its MCP Tools section to inspect the same evidence through structured calls.

Two Ways to Use Ansight Studio

Ansight Studio docs are split into two paths:

  • user-facing capabilities for people reviewing captures in Ansight Studio
  • MCP Tools for agents connected through the local bridge

User-Facing Capabilities

These pages describe what Ansight Studio lets a developer, tester, or reviewer do from the desktop app.

Setup

App Setup and Pairing

Register apps, link codebases, issue signed pairing configs, and generate QR pairing payloads.

Capture

Session Capture

Receive live sessions from paired devices and preserve logs, screenshots, touch input, telemetry, and state.

Review

Session Replay and Review

Reconstruct what happened with timelines, screenshots, logs, visual trees, touch input, and app state.

Review notes

Annotations

Add, edit, filter, and preserve review notes that are tied to moments, frames, and screen regions.

Metrics

Telemetry Review

Inspect FPS, memory, battery, lifecycle, and custom telemetry alongside logs and screenshots.

Handoff

Exports and Handoff

Create portable evidence bundles for bug reports, teammate review, or later investigation.

MCP Tools for Agents

Ansight Studio exposes host-owned MCP tools built into Ansight Studio itself. App-defined SDK tools are discovered at runtime by the live app bridge.

Open MCP Tools for the grouped agent-facing reference.

Install and Launch

Run Ansight Studio on the same trusted desktop machine as your AI client. Keep that machine on the same local network as the device or simulator you want to pair.

For MCP clients, prefer the stdio bridge:

ansight-daemon mcp-stdio

Ansight Studio also exposes a local HTTPS MCP endpoint for clients that cannot use stdio:

https://localhost:45125/mcp/

Use localhost rather than 127.0.0.1 so hostname validation matches the Ansight Studio certificate.

  1. Register the app in Ansight 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 capture the live session.
  6. Review the session timeline, logs, screenshots, telemetry, touches, annotations, and artifacts.
  7. Connect an MCP-capable agent when you want structured AI-assisted analysis.
  8. Export a session bundle when you need to hand evidence to another developer or revisit it later.