The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the OmniDebugLink listing page.
Remote debugging and automated testing on real devices — from anywhere.
Add a small client SDK to your app, connect it with a device token, and any AI coding tool (Claude Code, Cursor, Codex, Gemini CLI, …) can inspect and drive the running app over Model Context Protocol: dump the UI tree, take screenshots, tap, swipe, type, read logs, measure performance — no USB cable, no shared network, no emulator.
list_devices → run_task / device_status / list_tasks …| Platform | Install | Repo |
|---|---|---|
| Unity | Package Manager → add from git URL | omnidebuglink_unity |
| Android | JitPack: com.github.omnidebuglink:omnidebuglink_android:<tag> | omnidebuglink_android |
| Flutter | pubspec git dependency (ref: tag) | omnidebuglink_flutter |
| iOS / macOS | Swift Package (iOS 15+ / macOS 12+) | omnidebuglink_apple_swift |
| React Native | npm i omnidebuglink/omnidebuglink_react_native#<tag> | omnidebuglink_react_native |
| Godot | copy the addons/omni_debug_link/ folder (Godot ≥ 4.2) | omnidebuglink_godot |
| Web | CDN build via jsDelivr (@<tag>) | omnidebuglink_web |
Each SDK repo has the full install steps and task tables for its platform.
Pin a version tag (#vX.Y.Z / ref: / @vX.Y.Z) in production hosts.
Create a device token pair at the console (free during the public beta).
Connect your app: add the SDK for your platform and start it with the token — freely in debug builds; in release builds only via the conditional pattern (runtime-issued token, never embedded).
Add the MCP server to your AI tool (OAuth login in the browser):
Works with any MCP client: Cursor, Codex CLI, Gemini CLI, …
Ask the AI to list_devices and start driving the device.
sdk-integration.md is written to be handed to your AI coding tool verbatim — per-platform install and connect snippets, the rules that must not be broken, and a verification checklist. Ask the agent to read it and wire the SDK in.
Any platform with a WebSocket client can join — the wire protocol is a single JSON frame format:
→ Third-Party Client Development Guide — protocol spec, a portable reference implementation, known pitfalls, and a pre-deployment verification checklist. AI coding agents can implement a compliant client from this guide alone, without reading any SDK source.