Practical overview
When it fits
Use it when an AI client needs to interact with apps on an Android phone or emulator through the device's accessibility service and screenshots, rather than only processing app data through a separate API.
Who it is for
- Developers connecting MCP-compatible AI clients to an Android device.
- Teams building agent workflows that inspect or operate Android apps.
- Researchers and educators exploring AI-driven mobile interaction.
Documented uses
- Read Android UI elements and capture screenshots for an agent.
- Tap, swipe and enter text in apps on the device.
- Launch apps and manage files, including downloads.
- Expose an Android device's MCP endpoint through a network binding or supported tunnel.
Requirements & limits
The documented application targets Android devices and emulators. The repository displays an MIT license.
- Accessibility Service is mandatory for core UI inspection, actions and screenshots.
- The default server binding is 127.0.0.1; host access can use documented ADB port forwarding, while network binding or Cloudflare Quick Tunnels and ngrok are documented remote-access options.
- The app supports bearer-token authentication and OAuth 2.1, plus per-tool and per-parameter controls.
- Camera, microphone, location, notifications and file operations depend on relevant permissions or storage configuration.
- The project states that it is provided without warranty for research and educational purposes.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the Android MCP server in the app
Grant the required accessibility permission and start the server on an Android device or emulator.
Before you start
- Android device or emulator with the application installed.
- Accessibility Service permission.
Steps
Open the app and use the Server tab's permission warning or Settings > Permissions to enable Accessibility Service.
Grant optional permissions only for tools you intend to use; configure storage locations if using file tools.
Return to the Server tab and tap Start.
Read the connection information, including IP, port, token and URL, shown in the app.
Expected outcome
The MCP server starts on the device; the documented default endpoint is http://127.0.0.1:8080.
Guide limitations
- Accessibility Service is required for UI inspection, actions and screenshots.
- 127.0.0.1 refers to the Android device itself, not the host computer.
- A compatible MCP client still needs to be connected separately.
Connect through ADB port forwarding
Forward the device's default localhost server port to a host computer.
Before you start
- The app's MCP server is running on the Android device.
- ADB is available on the host and connected to the device.
Steps
Run
adb forward tcp:8080 tcp:8080on the host.Use the forwarded host endpoint at
http://localhost:8080/mcpfor MCP requests.Include the bearer token shown in the app's connection information when making a bearer-authenticated request.
Expected outcome
The host can address the device's MCP endpoint through the forwarded local port.
Guide limitations
- This recipe covers the documented ADB forwarding connection, not configuration of a particular AI client.
- The default server binding is localhost on the Android device.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- danielealbano/android-remote-control-mcp · Official homepage title · retained in its source language