Yunkai Phone Bridge
Provides a local-first bridge for bounded Android device perception and interaction over ADB, enabling device discovery, screenshots and UI hierarchy inspection, allowlisted key and app/URI actions, semantic/reflex UI observation with guarded verified taps, and passive health/status reporting for an authorized Android device.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Yunkai Phone Bridge
A local-first Android MCP bridge for bounded device perception and interaction over ADB.
This repository is a sanitized public-source export of the PhoneBridge used in the Yunkai project. It keeps the important control boundaries: read-only inspection first, a narrow ADB action surface, semantic/reflex UI targeting, deterministic verification, local policy, and passive health/status surfaces.
Highlights
Android device discovery and bounded ADB connectivity
screenshots and UI hierarchy inspection
allowlisted key and app-launch actions
semantic/reflex UI observation and guarded verified taps
passive health and runtime status
capability manifest, permission state, and unified device contract adapter
optional localhost-only vision fallback
companion-owned local integration surface
source-only Control Center helper
bounded Android 11+ wireless ADB recovery
Related MCP server: android-mcp-tools
Deliberate non-capabilities
The public bridge is not an arbitrary remote shell. It does not expose generic shell execution, root, APK installation, delete, uninstall, or clear-data tools.
Verified actions follow observe -> one action -> bounded re-observation -> report; they are not silently replayed after ambiguous results.
Public export boundary
This repository does not contain real tunnel IDs, runtime credentials, owner-specific configuration, caches, private verification captures, or tunnel-client/cloudflared binaries.
The shared contract modules required by the bridge are included under yunkai_shared/.
Requirements
Python 3.10+
Android Platform Tools /
adbinstalled locallyan Android device you are authorized to control, with ADB debugging enabled and paired/authorized
Python dependencies in
requirements.txt
Quick start
git clone https://github.com/YunkaiLim/yunkai-phone-bridge.git
cd yunkai-phone-bridge
py -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
adb devices
cd PhoneBridge
python server_stdio.pyFor the local HTTP entry point:
cd PhoneBridge
python server.pyOptional local vision can be configured by copying PhoneBridge/phonebridge_vision.example.json to phonebridge_vision.json. Reflex policy has a separate checked-in example file.
Tests
From PhoneBridge/:
python -m unittestDuring public-release preparation on 2026-09-30, the focused public suite passed 216 tests across core ADB behavior, local vision, wireless reliability, Reflex, passive health, companion-owned integration, and Control Center logic.
Live ADB/device acceptance still depends on your own authorized device, OEM behavior, and local Android tooling.
Security model
Read SECURITY.md. Keep ADB authorization under the device owner's control and do not broaden the bridge into arbitrary shell execution merely for convenience.
License
Apache-2.0. See LICENSE and NOTICE.
Third-party components remain under their own licenses; see THIRD_PARTY_NOTICES.md.
This project is independent source code and is not an official OpenAI product.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
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.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables an agent to inspect and interact with Android emulators or physical devices via ADB, capturing UI snapshots, tapping nodes, typing text, and reading app logs.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents and test runners to control Android devices via local ADB, including listing devices, tapping, swiping, typing, sending system keys, launching apps, and dumping UI hierarchy. Communicates over MCP stdio without exposing network listeners.-
- FlicenseBqualityBmaintenanceEnables comprehensive Android device control over ADB, including UI automation, screen capture/recording, app management, file operations, and log/notification access, with a built-in permission system.71-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices, with fast input, screenshots, UI element discovery, app and file management, shell access, and audio/video streaming or recording.392 npmMIT