About OmniDebugLink
OmniDebugLink connects real-device apps to AI coding tools for remote debugging and automated testing. Its platform SDKs connect to a relay, while MCP tools let agents inspect and operate devices without a USB cable or shared network.
Key features
- 01Inspect UI trees and screenshots
- 02Tap, swipe, and enter text
- 03Read logs and measure performance
- 04Connect apps through platform SDKs and a WebSocket relay
- 05List devices and manage tasks through MCP
Use cases
- 01Debug an app running on a remote device
- 02Automate interaction tests on real hardware
- 03Check logs and performance while reproducing an issue
MCP support
Provides an HTTP MCP server at the OmniDebugLink API for AI coding tools to list devices, run tasks, check device status, and list tasks. Apps connect to the relay using a platform SDK and a device token.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.omnidebuglink.dev/mcpclaude mcp add --transport http dev-omnidebuglink-omnidebuglink https://api.omnidebuglink.dev/mcp{"mcpServers":{"dev-omnidebuglink-omnidebuglink":{"type":"http","url":"https://api.omnidebuglink.dev/mcp"}}}Open in Cursor{"servers":{"dev-omnidebuglink-omnidebuglink":{"type":"http","url":"https://api.omnidebuglink.dev/mcp"}}}Open in VS Code{"mcpServers":{"dev-omnidebuglink-omnidebuglink":{"type":"http","url":"https://api.omnidebuglink.dev/mcp"}}}{"mcpServers":{"dev-omnidebuglink-omnidebuglink":{"serverUrl":"https://api.omnidebuglink.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEOmniDebugLink
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.
Your App ──wss──> OmniDebugLink relay ──MCP──> AI coding tool
- One outbound WebSocket from the device — works across networks, behind NAT, on real hardware.
- The AI side sees plain MCP tools:
list_devices→run_task/device_status/list_tasks… - One token pair = one device seat. Tokens are per-device; never embed one in a release build — release use goes through the conditional pattern.
Client SDKs
| 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.
Quickstart
-
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):
claude mcp add --transport http odl https://api.omnidebuglink.dev/mcpWorks with any MCP client: Cursor, Codex CLI, Gemini CLI, …
-
Ask the AI to
list_devicesand start driving the device.
Integrating an SDK into your app
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.
Building a client for another platform?
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.
Links
- Website · Console
- Third-party client guide
- SDK repositories: see the table above
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.