# OmniDebugLink

Remote debugging and automated tests on live hardware: UI tree, screenshots, taps, logs. No USB cable, no emulator.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: omnidebuglink
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/omnidebuglink/omnidebuglink
- Updated: 2026-09-08
- HTML: https://affpapa.org/en/nevibecode/mcp/omnidebuglink

## What it 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.

## Requirements
- Remote server: `https://api.omnidebuglink.dev/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http omnidebuglink https://api.omnidebuglink.dev/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add omnidebuglink --url https://api.omnidebuglink.dev/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "omnidebuglink": {
            "url": "https://api.omnidebuglink.dev/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "omnidebuglink": {
            "type": "http",
            "url": "https://api.omnidebuglink.dev/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http omnidebuglink https://api.omnidebuglink.dev/mcp
```

## When to use it
- 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
- 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

## Similar
- [levelplay-unity-integration](https://affpapa.org/en/nevibecode/skills/levelplay-unity-integration.md) — skill · 5900 installs
- [mobile-app-debugging](https://affpapa.org/en/nevibecode/skills/mobile-app-debugging.md) — skill · 561 installs
- [unity-pipeline](https://affpapa.org/en/nevibecode/skills/unity-pipeline.md) — skill · 1200 installs
- [unity-game-developer](https://affpapa.org/en/nevibecode/agents/unity-game-developer.md) — subagent · 1122 installs
- [test-setup](https://affpapa.org/en/nevibecode/skills/test-setup.md) — skill · 411 installs
- [test-flakiness](https://affpapa.org/en/nevibecode/skills/test-flakiness.md) — skill · 408 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md