
Expo Android MCP
io.github.frndchagasPublished by GitHub account frndchagasv0.5.2Updated Oct 24, 2026
MCP server for Android emulator automation via ADB.
Overview
A local MCP server that lets an assistant inspect and drive Android emulators or devices through ADB, including taps, swipes, text input and app launches.
- What you can do
- List and select connected devices and emulators, and check that ADB is reachable and working properly (doctor). Dump the current screen into parsed UI elements, optionally with a screenshot, and find, wait for or assert elements by text, content description, resource ID or class. Tap elements or raw coordinates, swipe, long-press, type text into the focused field and send Android key events. Launch apps by package name, list installed packages, and download and install the pinned Expo Go APK.
- When to use it
- Useful when you want an assistant to test or navigate an Android app or Expo project on an emulator or connected device: inspecting screens, driving the UI, and checking that expected elements appear. It fits local development and QA workflows rather than general phone use.
- Requirements
- Runs locally via npm (Node 18+) or a one-click desktop bundle. Needs Android SDK platform-tools (adb) available, and an emulator or device connected. Optional environment variables: ADB_PATH, ADB_SERIAL, ADB_TIMEOUT_MS, ADB_MAX_BUFFER_MB, ADB_DEBUG, MCP_TRANSPORT and PORT. No authentication is declared.
Installation
In SourceWeft
- Open Expo Android MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
expo-android
[npm version] [npm downloads] [license] [node version] [typescript] [CI]
MCP server for Android emulator automation via ADB.
Requirements
- Node 18+
- Android SDK platform-tools (adb) available
- Android emulator or device connected
Verify adb:
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:
Quickstart
- Start an emulator or connect a device.
- Run
doctorto validate adb + device selection. - Use
inspect,tapElement,inputText, etc.
Example:
Use with Claude Code CLI
Use with OpenAI Codex CLI
Or edit ~/.codex/config.toml:
Serial selection priority:
serial param (per tool call) → setDevice override → ADB_SERIAL env → auto (if only one device).
Environment variables
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:
If multiple devices are connected, set ADB_SERIAL to the target device.
You can also run setDevice at runtime:
If you update PATH or SDK variables, restart the MCP process so it can pick up the new environment.
Tests
Tools
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
Inspect options:
includeScreenshot(default:false)screenshotMode:base64orpathscreenshotPath: optional file path when usingpathmaxElements: limit elements returnedincludeElements: return elements or summary only
Doctor
Override serial per call
Tap element
Wait + assert
Source: README.md at commit 11bf4d0
Tools
0Version history
1- v0.5.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts