expo-android
Provides tools for automating Android emulators and devices via ADB, including UI inspection, element interaction, and device management.
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., "@expo-android list connected devices"
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.
expo-android
MCP server for Android emulator automation via ADB.
Requirements
Node 18+
Android SDK platform-tools (adb) available
Android emulator or device connected
Verify adb:
adb devicesRelated MCP server: android-mcp-server
Install
Claude Desktop, one-click: download expo-android.mcpb from the latest release and drag it into Settings → Extensions. You can leave both fields empty — adb is auto-detected and the only connected device is used by default.
Via npm:
npm install -g @fndchagas/expo-android
# or
npx -y @fndchagas/expo-androidQuickstart
Start an emulator or connect a device.
Run
doctorto validate adb + device selection.Use
inspect,tapElement,inputText, etc.
Example:
await client.callTool({ name: 'expo-android.doctor', arguments: {} });
await client.callTool({
name: 'expo-android.inspect',
arguments: { onlyInteractive: true, maxElements: 200 },
});Use with Claude Code CLI
claude mcp add expo-android \
--env ADB_PATH="$HOME/Library/Android/sdk/platform-tools/adb" \
--env ADB_SERIAL="auto" \
-- npx -y @fndchagas/expo-androidUse with OpenAI Codex CLI
codex mcp add expo-android \
--env ADB_PATH="$HOME/Library/Android/sdk/platform-tools/adb" \
--env ADB_SERIAL="auto" \
-- npx -y @fndchagas/expo-androidOr edit ~/.codex/config.toml:
[mcp_servers.expo-android]
command = "npx"
args = ["-y", "@fndchagas/expo-android"]
env = { ADB_PATH = "/Users/you/Library/Android/sdk/platform-tools/adb", ADB_SERIAL = "emulator-5554" }Serial selection priority:
serial param (per tool call) → setDevice override → ADB_SERIAL env → auto (if only one device).
Environment variables
Variable | Default | Description |
|
| Path to adb executable |
| optional | Device serial to target ( |
|
| Timeout for adb commands |
|
| Max output buffer size |
|
| Log adb diagnostics to stderr |
|
| Transport: |
|
| HTTP port when using http/both |
Troubleshooting
adb not found (spawn adb ENOENT)
The server starts even when adb is missing — tools return the ADB executable not found
error until adb becomes reachable (run doctor to diagnose). To fix it, set ADB_PATH
or export an SDK path:
export ADB_PATH="$HOME/Library/Android/sdk/platform-tools/adb"
# or
export ANDROID_HOME="$HOME/Library/Android/sdk"If multiple devices are connected, set ADB_SERIAL to the target device.
You can also run setDevice at runtime:
await client.callTool({
name: 'expo-android.setDevice',
arguments: { serial: 'emulator-5554' },
});If you update PATH or SDK variables, restart the MCP process so it can pick up the new environment.
Tests
npm run build
npm testTools
Tool names are plain identifiers (e.g. tap); your MCP client prefixes them with the server name you registered.
devices— list connected devices and emulators.doctor— validate adb availability and show connected devices.setDevice— override the active device serial for this MCP process.inspect— UI dump parsed into elements with a summary (screenshot optional).screenshot— capture a screenshot only (base64 or file path).findElement— return elements that match search criteria.tapElement— find an element and tap its center.waitForElement— wait until an element appears (optionally with state checks).assertElement— verify element existence and state.tap— tap at x/y coordinates.swipe— swipe between coordinates.longPress— press and hold at coordinates.inputText— type text in the focused field.keyEvent— send Android key events (e.g., BACK, HOME).openApp— launch an app by package name.listPackages— list installed package names.installExpoGo— download the pinned Expo Go APK and install it viaadb install -r(theurloverride only accepts officialgithub.com/expo/expo-go-releasesURLs).
Every tool declares MCP annotations (readOnlyHint/destructiveHint), so clients can auto-approve inspection tools and gate the ones that drive the device.
Search criteria
These tools accept flexible search inputs: findElement, tapElement,
waitForElement, assertElement.
Common fields:
text,textContainscontentDesc,contentDescContainsresourceId,resourceIdContainsclassnormalizeWhitespace,caseInsensitive
MCP usage examples
Inspect
const result = await client.callTool({
name: 'expo-android.inspect',
arguments: { onlyInteractive: true, includeScreenshot: false, maxElements: 200 },
});Inspect options:
includeScreenshot(default:false)screenshotMode:base64orpathscreenshotPath: optional file path when usingpathmaxElements: limit elements returnedincludeElements: return elements or summary only
Doctor
await client.callTool({
name: 'expo-android.doctor',
arguments: {},
});Override serial per call
await client.callTool({
name: 'expo-android.tapElement',
arguments: { text: 'Search', serial: 'emulator-5554' },
});Tap element
await client.callTool({
name: 'expo-android.tapElement',
arguments: { text: 'Private account' },
});Wait + assert
await client.callTool({
name: 'expo-android.waitForElement',
arguments: { text: 'Save', timeout: 10000, shouldBeClickable: true },
});
await client.callTool({
name: 'expo-android.assertElement',
arguments: { text: 'Private account', shouldBeChecked: true },
});Available Tools
17 toolsassertElementAssert elementCRead-only
Assert element presence and state.
Inputs: text, class, serial, resourceId, +10 more.
devicesList devicesARead-only
List connected Android devices and emulators.
Inputs: no named parameters.
doctorDoctorBRead-only
Check adb availability and connected devices.
Inputs: no named parameters.
findElementFind elementCRead-only
Find UI elements by criteria.
Inputs: text, class, serial, checkable, +8 more.
inputTextInput textC
Type text into the focused input field.
Inputs: text (required), serial.
inspectInspectBRead-only
Capture a screenshot and parse UI hierarchy into structured elements.
Inputs: serial, maxElements, screenshotMode, screenshotPath, +3 more.
installExpoGoInstall Expo GoA
Download the pinned Expo Go APK and install it on the device via adb install -r. Pass url to install a different official Expo Go release (only github.com/expo/expo-go-releases URLs are accepted).
Inputs: url, serial.
keyEventKey eventC
Send an Android key event to the device.
Inputs: keyCode (required), serial.
listPackagesList packagesBRead-only
List installed package names.
Inputs: filter, serial.
longPressLong pressC
Press and hold on screen at coordinates.
Inputs: x (required), y (required), serial, duration.
openAppOpen appB
Launch an Android app by package name.
Inputs: packageName (required), serial.
screenshotScreenshotARead-only
Capture a screenshot without UI element parsing.
Inputs: mode, path, serial.
setDeviceSet deviceAIdempotent
Override the active device serial for this MCP process. Use "auto" to clear override.
Inputs: serial.
swipeSwipeB
Swipe on screen from one coordinate to another.
Inputs: x1 (required), x2 (required), y1 (required), y2 (required), +2 more.
tapTapC
Tap on screen at coordinates.
Inputs: x (required), y (required), serial.
tapElementTap elementC
Find an element and tap its center coordinate.
Inputs: text, class, index, serial, +8 more.
waitForElementWait for elementBRead-only
Wait until an element appears or timeout is reached.
Inputs: text, class, serial, timeout, +11 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Most tools are clearly distinct, such as screenshot vs. inspect (with UI parsing) and coordinate-based tap vs. element-based tapElement. Minor overlap exists between devices and doctor, both listing devices, but descriptions differentiate their purposes.
Naming mixes imperative verbs (tap, swipe, inspect) with verb+noun compounds (findElement, openApp) and a few noun-only names (devices, doctor). The pattern is not fully consistent but remains readable and predictable.
At 17 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct function in device management, UI interaction, and app handling. The count feels justified for a comprehensive Android automation server.
The toolset covers core device lifecycle, UI inspection/interaction, and Expo Go installation. Minor gaps include lack of arbitrary APK installation or text clearing, but essential workflows are well represented.
Maintenance
Related MCP Connectors
MCP server for Appcircle mobile CI/CD platform.
MCP server to assist with JxBrowser development.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for Android device automation via ADB, enabling screen control, phone functions, app management, and device control.301MIT
- FlicenseNot gradedqualityDmaintenanceA powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for controlling Android devices over ADB, using direct commands and semantic accessibility selectors with a Kotlin helper APK.444 npmMIT
- FlicenseAqualityCmaintenanceMCP server for controlling Android, Fire TV, and Android TV devices through ADB, enabling device management, app operations, screenshots, UI dumps, and OBS recording.301-