OmniDebugLink — Claude Code MCP server: debug on real devices
Remote debugging and automated tests on live hardware: UI tree, screenshots, taps, logs. No USB cable, no emulator.
claude mcp add --transport http omnidebuglink https://api.omnidebuglink.dev/mcpWhat OmniDebugLink does
OmniDebugLink puts a running app in front of your AI coding tool over MCP. You add a small client SDK to the app, it opens one outbound WebSocket to the relay, and the agent gets plain MCP tools: list_devices, run_task, device_status, list_tasks. The connection survives NAT and separate networks.
SDKs cover Unity, Android, Flutter, iOS and macOS, React Native, Godot and Web. Each platform installs its own way: JitPack for Android, Swift Package for Apple, a git dependency in pubspec for Flutter, the addons/omni_debug_link/ folder for Godot. For production hosts the advice is to pin a version tag.
A token pair maps to one device seat, and it must not be baked into a release build — release use goes through a conditional pattern where the token is issued at runtime. You create the pair in the console, free while the public beta runs. If your platform has no SDK yet, a protocol guide lets an agent write a compliant client without reading SDK sources.
What it helps with
- inspect the UI tree of a running app on real hardware
- grab a screenshot without plugging in a cable
- drive taps, swipes and text input on a physical phone
- read logs and measure performance while the app runs
- hook device debugging into an agent over MCP
Example prompts for the agent
- List the connected devices with
list_devices - Take a screenshot and dump the current UI tree
- Tap the login button and send me the logs
How to install OmniDebugLink
Platform CLI: remote server
claude mcp add --transport http omnidebuglink https://api.omnidebuglink.dev/mcpPlatform CLI: remote server
codex mcp add omnidebuglink --url https://api.omnidebuglink.dev/mcpConfig file
{
"mcpServers": {
"omnidebuglink": {
"url": "https://api.omnidebuglink.dev/mcp"
}
}
}Config file
{
"servers": {
"omnidebuglink": {
"type": "http",
"url": "https://api.omnidebuglink.dev/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http omnidebuglink https://api.omnidebuglink.dev/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about OmniDebugLink
How do I install OmniDebugLink in Claude Code?
Run claude mcp add --transport http omnidebuglink https://api.omnidebuglink.dev/mcp, then complete the OAuth login in your browser. After that ask the agent to call list_devices.
What does OmniDebugLink do?
It gives an AI agent access to a running app on a real device: UI tree, screenshots, taps, swipes, typing, logs and performance readings. Everything travels over a single outbound WebSocket to the relay.
Can I ship the device token in a release build?
No. One token pair equals one device seat, so it should never be embedded in a release build — production uses a conditional pattern with a runtime-issued token.
