expo-android
MCP server for Android emulator automation via ADB.
README
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 devices
Install
npm install -g @fndchagas/expo-android
# or
npx -y @fndchagas/expo-android
Quickstart
- 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-android
Use 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-android
Or 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 |
|---|---|---|
ADB_PATH |
adb |
Path to adb executable |
ADB_SERIAL |
optional | Device serial to target (auto to clear and auto-detect) |
ADB_TIMEOUT_MS |
15000 |
Timeout for adb commands |
ADB_MAX_BUFFER_MB |
10 |
Max output buffer size |
ADB_DEBUG |
0 |
Log adb diagnostics to stderr |
MCP_TRANSPORT |
stdio |
Transport: stdio, http, or both |
PORT |
7332 |
HTTP port when using http/both |
Troubleshooting
adb not found (spawn adb ENOENT)
If you see an error like ADB executable not found or spawn adb ENOENT, 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 test
Tools
Tools are exposed under your MCP server name. Example: expo-android.tap.
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.
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 },
});
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。