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.
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., "@Yunkai Phone Bridgetake a screenshot and inspect the UI of my phone"
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.
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/URI 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
Related MCP server: ThumbAgent
Deliberate non-capabilities
The public bridge is not an arbitrary remote shell. Keep ADB authorization under the device owner's control and preserve the existing action, identity, policy, and verification gates.
Public export boundary
This repository does not contain real tunnel IDs, runtime credentials, owner-specific configuration, caches, local verification captures, or tunnel-client binaries. The private secure-tunnel launchers and bundled cloudflared executables are intentionally omitted from this first public source release.
The shared contract modules required by the bridge are included under yunkai_shared/.
Requirements
Python 3.11+
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 used by the original bridge:
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 unittestThe private working tree passed 217 unit tests immediately before this public export. Live ADB/device acceptance still depends on the user's own authorized device and local Android tooling.
Security model
Read SECURITY.md. Do not broaden this bridge into arbitrary shell execution merely for convenience; the narrow surface is intentional.
License
Apache-2.0. See LICENSE and NOTICE.
This project is independent source code and is not an official OpenAI product.
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.
Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.
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
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that enables AI agents to safely control and observe Android mobile devices, supporting device diagnostics, app lifecycle management, async task execution, and performance monitoring through a policy-constrained interface with explicit confirmations.Apache 2.0
- 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-