Data as of
Android MCP Server for VS Code: Setup & Config
VS Code: Android MCP Server exposes ADB-based device operations to MCP clients.
What you can do with Android in VS Code
Pick it for direct ADB access paired with screenshot and clickable-UI inspection.
- Inspect clickable UI elements and their screen coordinates
- List installed packages and inspect package actions
Before you start: Android in VS Code
- Python 3.x; setup example installs 3.11
- uv
- ADB installed and configured
- An Android device; emulator support is untested
Replace both path placeholders. Clone the repository and run uv sync first. Select a device in config.yaml when more than one is attached.
Android VS Code configuration
Choose VS Code configuration scope
For Android MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add Android MCP Server to VS Code
Use the android-mcp-server entry below in servers. Keep Android MCP Server's documented stdio connection fields and your other VS Code entries.
Check Android MCP Server in VS Code
Android MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"android-mcp-server": {
"type": "stdio",
"command": "path/to/uv",
"args": [
"--directory",
"path/to/android-mcp-server",
"run",
"server.py"
],
"env": {}
}
}
}Android tools available to VS Code
Android's stored tool list documents 5 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.
- get_packages
Look for get_packages among VS Code's agent-mode tools after starting Android through the MCP controls.
- execute_adb_command
Look for execute_adb_command among VS Code's agent-mode tools after starting Android through the MCP controls.
Run an ADB command and return its output.
- get_uilayout
Look for get_uilayout among VS Code's agent-mode tools after starting Android through the MCP controls.
Inspect clickable UI elements, including bounds and center coordinates.
- get_screenshot
Look for get_screenshot among VS Code's agent-mode tools after starting Android through the MCP controls.
Capture the current device screen.
- get_package_action_intents
Look for get_package_action_intents among VS Code's agent-mode tools after starting Android through the MCP controls.
Troubleshooting Android in VS Code
- Make uv available in the workspace, container, or remote environment hosting Android MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
- Android MCP Server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Known limitation: Emulator use is marked untested
- Known limitation: Requires ADB installation and a connected device
- General VS Code troubleshooting lives in the /clients/vscode guide.
Android MCP Server — details. VS Code guide