Provides real-time Android device debugging capabilities including connection status, screenshots/frames, logs, and more via ADB and Tango.
Provides real-time HarmonyOS device debugging capabilities including connection status, screenshots, logs, and more via HDC, UITest, and HiLog.
Provides real-time iOS device debugging capabilities including connection status, screenshots/frames, logs, and more via go-ios on physical devices.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@cross-dev-mcp list connected devices and show their real-time status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cross-platform real-device debugging MCP for React Native local development. V1 supports Android, iOS, and HarmonyOS real devices, prioritizing real-time connection status, screenshots/frames, logs, Doctor, Evidence, and Codex context callbacks.
See the full design and roadmap in docs/cross-dev-mcp-design-and-roadmap.md.
Codex / MCP Host
├─ stdio MCP tools
└─ Vue 3 MCP App
│ REST + WebSocket
Hono Daemon
│ unified TypeScript API
CrossDevService
├─ Android: Tango + Google ADB Server（无 scrcpy）
├─ iOS: go-ios（仅真机）
└─ HarmonyOS: 官方 HDC / UITest / HiLog（仅真机）Device capabilities are implemented through Provider, and the application layer only uses unified protocols such as RuntimeTarget, RawFrame, and NormalizedLogRecord. DOM/element inspection only retains the future interface boundary and is not part of the current P0.
Related MCP server: React Native Debug MCP
pnpm install
pnpm devpnpm dev starts both the device Daemon at http://127.0.0.1:4110 and the Vue/Vite development page at http://127.0.0.1:5173. The MCP frontend has two modes:
# 调试模式：从 Vite 加载实时源码并启用 HMR
pnpm mcp:dev
# 正式模式：读取 apps/dashboard/dist 构建产物
pnpm build
pnpm mcpCommon verification:
pnpm typecheck
pnpm test
pnpm buildThe Daemon default address is http://127.0.0.1:4110. The Dashboard can be opened independently, and can also be opened in Hosts that support MCP Apps via the MCP tool mobile_open_dashboard.
To demo the UI without a real device, you can temporarily use CROSS_DEV_FAKE=1 pnpm dev:daemon; production/MCP startup does not register the Fake Provider by default.
You can register the stdio MCP directly on the current machine:
codex mcp add cross-dev-mcp -- \
pnpm --silent --dir /Users/didi/VscodeProjects/phone-dev-mcp mcp:devThe registration above is for local debugging and lets the Codex MCP App load the Vite live source directly. For production use, change mcp:dev at the end to mcp. After restarting or refreshing the Codex MCP list, you can call mobile_open_dashboard to open the workbench. If the project moves to another directory, update the absolute path in the command accordingly.
See the corresponding packages/*/README.md for each subpackage's responsibilities, APIs, platform principles, and verification commands; all public and key implementation methods use Chinese JSDoc.
Only 127.0.0.1 is listened on by default. Device write operations, signing, installation, tunneling, and privilege escalation are not executed without confirmation.
截取真机画面并返回节省 token 的压缩图片。
Inputs: targetId (required), format, quality, maxWidth.
运行 ADB、go-ios 和官方 HDC 的平台专项连接诊断，可指定单台设备。
Inputs: targetId.
读取已连接真机的标准化原生日志，支持按级别和文本筛选。
Inputs: targetId (required), level, limit, preset, +2 more.
通过所选平台适配器发送经过校验的点击、滑动、文本输入或按键操作。
Inputs: action (required), targetId (required).
列出 Android、iOS 与 HarmonyOS 真机及其实时连接状态和能力状态。
Inputs: no named parameters.
打开 cross-dev-mcp 实时真机工作台。Codex Desktop 调用后应读取 dashboardUrl，并直接在右侧内嵌浏览器中打开；其他兼容宿主使用关联的 MCP App。
Inputs: no named parameters. Returns: title, dashboardUrl, presentation, dashboardMode
读取 Dashboard 暂存的证据包，其中包含压缩并标注的画面及所选日志。
Inputs: evidenceId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool targets a clearly distinct action: listing devices, capturing screens, reading logs, running diagnostics, sending interactions, reading evidence, and opening the dashboard. There is no meaningful overlap or ambiguity between tool purposes.
Tool names mostly follow a consistent mobile_<verb>_<noun> pattern, e.g. mobile_list_targets, mobile_get_logs, mobile_read_evidence. Minor deviations like mobile_capture and mobile_doctor lack a clear noun or use a noun-like verb, but the overall pattern is predictable.
Seven tools is well-scoped for a real-device testing and debugging server. Each tool serves a distinct workflow step without unnecessary bloat or duplication.
The tool surface covers the core lifecycle of device discovery, interaction, capture, logs, diagnostics, and evidence retrieval. Minor gaps exist, such as no explicit app installation/launch or file transfer operations, but the provided set supports a coherent testing workflow.
remote debug iOS/Android/Unity/Godot/Flutter/RN/Web on real-device.ui-tree/screenshots/taps,tests.
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Drive and test your React Native and Expo apps end-to-end on iOS and Android. Supports real devices, simulators, and emulators. Snapshots, taps, typing, swipes, screenshots, deep links, reloads, builds and runtime errors.
Flutter in-app bug tracking, visual pin annotations, and device logs directly into your AI IDE.
