Let AI debug and test your app on real devices — from anywhere

OmniDebugLink relays your AI coding tool straight to your app running on a real device, over the internet. No same Wi-Fi, no USB cable. Traverse the UI tree, take screenshots, inspect components, tap buttons, run automated end-to-end test flows — synchronous MCP calls, what you see is what you get.

Get started — free Quick start

Free during the public beta.

Capabilities

Truly remote

Device and AI tool can be on different networks, cities, or continents. Traffic relays through a global edge network — no LAN, no tethering, no port forwarding.

7 official SDKs

Unity, Android, iOS / macOS, Flutter, React Native, Godot, and Web (JavaScript). One-line integration on every platform.

UI & scene introspection

Full runtime hierarchy: Unity scenes, native view trees, Flutter element trees, Godot scene trees, and the DOM (shadow DOM included).

Real-device screenshots

Native image blocks streamed back to the AI — it sees exactly what's on screen, with minimal token cost.

Real input injection

Taps, swipes, and keys go through the platform's real event pipeline — equivalent to a finger on the screen, not a mock.

Synchronous MCP

Tool calls block until the device replies: the AI gets data, not callbacks. Relayed across 11 global regions for low latency, wherever you are.

All capabilities →

Platforms

Unity

UPM package — Package Manager → Add from git URL.

Get started →

Android

Kotlin AAR via JitPack. Compose bridge included.

Get started →

iOS · macOS

Swift Package, one package for both Apple platforms.

Get started →

Flutter

Pure Dart package, zero native setup.

Get started →

React Native

TS protocol layer + Kotlin/Swift native bridge (autolinking).

Get started →

Godot

GDScript addon for Godot ≥ 4.2, zero dependencies.

Get started →

Web (JavaScript)

Pure ES module via CDN, shadow DOM supported.

Get started →

All platforms →

Quick start

1

Create a token pair in the console

Sign up, create a token pair, and pick the region closest to your device.

clientToken  → used by the on-device SDK
AI tool      → account sign-in, no token needed (see step 3)
2

Integrate the SDK into your app

Pick your platform above — every SDK is a one-line start(clientToken) call with reconnect and heartbeat built in.

OmniDebugLink.start("<clientToken>");  // same idea on all 7 platforms
3

Connect your AI tool via MCP

No token to copy — a browser sign-in pops up on first use, then the AI can drive every device under your account.

claude mcp add --transport http odl \
  "https://api.omnidebuglink.dev/mcp"

Frequently asked questions

What is OmniDebugLink?

A relay that connects your AI coding tool to your app on a real device over the internet — synchronous MCP calls, real data back.

Same network needed?

No. The device SDK dials out to the relay; your AI tool connects to the same relay. Both sides are outbound-only — no shared Wi-Fi, USB, or port forwarding.

Do I paste a token into my AI tool?

No. Connect your MCP client and sign in once in the browser — then it can drive every device on your account.

What data goes through the relay?

Only what your AI asks for: UI trees, screenshots, logs, and input events. Traffic is encrypted in transit, and you can revoke access anytime from the console.

What does it cost?

Nothing right now — free during the public beta.

Can it run automated tests?

Yes — an AI agent can drive repeatable E2E test flows on real devices: UI, screenshots, logs, assertions. No test framework to maintain.

All questions →