Server facts
Android MCP Server
Project
- Author
- minhalvp
- Repository
- github.com/minhalvp/android-mcp-server
- License
- Apache-2.0
- Category
- Mobile & Desktop Automation
Tech
- Runtime / language
- pythonPython
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 811
- Last commit
- Data as of
Tags
- Adb
- Android
- Device Control
- Ui Inspection
Overview
Android MCP Server gives MCP clients access to an Android device through Android Debug Bridge. It targets workflows where an assistant needs device information or command execution rather than only source code context. The documented tools list installed packages, execute ADB commands, capture the current screen, and inspect the active user interface. UI inspection reports clickable elements together with text, content descriptions, bounds, and center coordinates. A separate package tool retrieves non-data actions from the Activity Resolver Table, adding another way to understand how an installed application can be addressed. Claude Desktop and Cursor are given as example clients.
Device selection is deliberately simple when only one device is attached: the server can choose it without a configuration file. With several connected devices, users must specify a serial in the optional config.yaml file; otherwise the server reports the available devices instead of silently choosing one. The README explains how to obtain that identifier with adb devices. Setup requires Python, a configured ADB installation, and an Android target. The project uses uv for dependency management and documents installing Python 3.11 before synchronizing dependencies. Client configuration launches server.py from the repository directory. Emulator use is mentioned but marked untested, which is an important qualification when planning a test environment.
Install & configure
Requirements
- Python 3.x; setup example installs 3.11
- uv
- ADB installed and configured
- An Android device; emulator support is untested
path/to/uv --directory path/to/android-mcp-server run server.pyReplace both path placeholders. Clone the repository and run uv sync first. Select a device in config.yaml when more than one is attached.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"android-mcp-server": {
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"android-mcp-server": {
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"android-mcp-server": {
"type": "stdio",
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"android-mcp-server": {
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"android-mcp-server": {
"type": "stdio",
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| get_packages | List packages installed on the selected device. |
| execute_adb_command | Run an ADB command and return its output. |
| get_uilayout | Inspect clickable UI elements, including bounds and center coordinates. |
| get_screenshot | Capture the current device screen. |
| get_package_action_intents | Retrieve non-data activity actions for a package. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Inspect clickable UI elements and their screen coordinates
- Capture device screenshots for assistant review
- List installed packages and inspect package actions
- Run ADB commands from an MCP client
Strengths
- Automatically selects a sole connected device
- Exposes screenshots and structured clickable-element details
- Allows explicit serial selection for multi-device setups
Limitations
- Emulator use is marked untested
- Requires ADB installation and a connected device
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.