Allows LLM agents to control an Android device securely via Shizuku (rish) and Termux:API, providing shell execution, session management, and artifact handling.
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., "@android-shizuku-mcp show device model and Android version"
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.
An open-source Model Context Protocol (MCP) server for Android, running in Termux. It allows LLM agents to control your Android device securely via Shizuku (rish) and Termux:API.
Streamable HTTP Transport: Modern MCP transport for robust communication.
Single Universal Shell Tool: One MCP tool for Termux and rish, designed to feel closer to a real terminal.
Hybrid Exec + Session Model: The same shell tool supports one-shot commands and persistent shell sessions.
Raw Inline First: If stdout/stderr fit the budget, they are returned whole instead of being split into preview sections.
Long-Running Recovery: One-shot commands can still be polled/cancelled when they outlive the sync budget.
Interactive Session Flow: Sessions support write/read/close on a persistent shell cursor.
Shizuku Integration: High-privilege Android commands can be routed through rish.
Low-Context UX: Error payloads stay short and operational for weak LLMs.
Artifact Management: Command/session output is persisted for follow-up inspection when needed.
Related MCP server: Termux MCP Server
Termux: Install from F-Droid.
Termux:API: Install both the app (F-Droid) and the package (pkg install termux-api).
Shizuku: Set up on your device (Wireless Debugging or Root).
rish: Copy rish to your Termux home directory (~/bin/rish) and ensure it's executable and not writable by others (on Android 14+).
Clone this repository in Termux.
Run the installation script:
./install.shCopy the Bearer token from the .env file created.
Start the server:
./run-server.shBy default, the server runs on http://127.0.0.1:8765/mcp.
Use the following configuration (e.g., in Claude Desktop):
{
"mcpServers": {
"android": {
"command": "python",
"args": ["/path/to/android-shizuku-mcp/src/main.py"],
"env": {
"MCP_AUTH_TOKEN": "your-token-here"
}
}
}
}Or connect via HTTP directly using an MCP client supporting Streamable HTTP.
Shell: shell is the primary universal tool. It supports exec, poll, open_session, write, read, close, and cancel.
System: doctor
Artifacts: list_artifacts
Run ./setup_boot.sh to create a Termux:Boot script. Ensure the Termux:Boot app is installed.
Bind to 127.0.0.1 unless you intentionally expose the server another way.
Bearer token authentication is supported and recommended.
The shell path is permissive by design and is not a command-policy sandbox.
The server is optimized for low-friction command execution and low-context responses, not strict shell filtering.
Apache-2.0
This server cannot be deployed
Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Melaya is a remote MCP server. It gives an assistant hands on your own Android phone and browser: it reads the screen through the accessibility tree, then taps, types and navigates inside the apps and sites you allow-list, with no per-app API. It also builds, schedules and runs agent pipelines across 6k+ connected tools. OAuth 2.1, nothing to install.
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.
