android-shizuku-mcp
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 "Install 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-mcpshow 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.
android-shizuku-mcp
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.
Features
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
shelltool 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: adb-mcp-server
Prerequisites
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
rishto your Termux home directory (~/bin/rish) and ensure it's executable and not writable by others (on Android 14+).
Installation
Clone this repository in Termux.
Run the installation script:
./install.shCopy the Bearer token from the
.envfile created.
Usage
Start the server:
./run-server.shBy default, the server runs on http://127.0.0.1:8765/mcp.
Connecting an MCP Client
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.
Available Tools
Shell:
shellis the primary universal tool. It supportsexec,poll,open_session,write,read,close, andcancel.System:
doctorArtifacts:
list_artifacts
Autostart
Run ./setup_boot.sh to create a Termux:Boot script. Ensure the Termux:Boot app is installed.
Security
Bind to
127.0.0.1unless 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.
License
Apache-2.0
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
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.
Remote shell and detached long-running jobs on your own machines — no SSH, open ports or VPN.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to control and manage Android devices via ADB, including app installation, UI interaction, and device monitoring.12GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.13MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to directly control Android devices via Termux, providing 120+ tools for screen manipulation, file management, app control, and system operations with layered loading and security gating.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI models to control Android devices via ADB through natural language commands, supporting screen analysis and automated actions.31MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shizzgar/shizuku-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server