omnidebuglink

Remotely debug and test your app on a real device from any AI editor — no USB cable, no shared WiFi, works behind NAT.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • List Devices: List the device token pairs this connection can drive (name, sid, region, online). Call this FIRST; when several devices exist, ask the user which one to use and pass its name or sid as
  • Device Detail: Full info for one device, including its clientToken and a ready-to-paste Unity connect snippet. Only call this when the user explicitly asks for the token or connect instructions.
  • Device Status: Check whether the target device is connected to the relay.

What data it sees

Do you need an account

No: the server works without sign-in

Remotely debug and test your app on a real device from any AI editor — no USB cable, no shared WiFi, works behind NAT. Official client SDKs for Unity, Godot, Flutter, iOS/macOS, Android, React Native, and Web; any WebSocket-capable platform can join via the open protocol.

How to connect

How to connect omnidebuglink to Claude

The server address to paste into Claude settings:

https://omnidebuglink--zhoulunjie96.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect omnidebuglink to ChatGPT

The server address to paste into ChatGPT settings:

https://omnidebuglink--zhoulunjie96.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect omnidebuglink to Cursor

The server address to paste into Cursor settings:

https://omnidebuglink--zhoulunjie96.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

list_devicesList the device token pairs this connection can drive (name, sid, region, online). Call this FIRST; when several devices exist, ask the user which one to use and pass its name or sid as the "device" argument on subsequent tool calls. Tokens are NOT included — use device_detail when the user asks for connect instructions.
device_detailFull info for one device, including its clientToken and a ready-to-paste Unity connect snippet. Only call this when the user explicitly asks for the token or connect instructions.
device_statusCheck whether the target device is connected to the relay.
device_pingRound-trip ping to the connected device; measures relay + device latency.
list_tasksDiscover what the connected device client can do: returns its task manifest (task types with descriptions and payload schemas) as reported by the device build. Call this before run_task when unsure which task types exist.
run_taskSend a task to the connected device over the debug relay and wait synchronously for its result.