Expo Android MCP

io.github.frndchagas由 GitHub 账号 frndchagas 发布v0.5.2更新于 Oct 24, 2026

MCP server for Android emulator automation via ADB.

已验证STDIO仅桌面浏览器自动化开发者工具

概览

AI 生成的概览

本地 MCP 服务器,让助手通过 ADB 检查并操作 Android 模拟器或设备,包括点击、滑动、输入文字和启动应用。

可以做什么
列出并选择已连接的设备和模拟器,并检查 ADB 是否可用、工作是否正常(doctor)。将当前屏幕导出为解析后的 UI 元素,可选附带截图,并按文字、内容描述、资源 ID 或类名查找、等待或断言元素。点击元素或原始坐标、滑动、长按、在焦点输入框中输入文字,并发送 Android 按键事件。按包名启动应用、列出已安装的包,并下载和安装固定版本的 Expo Go APK。
适用场景
适合让助手在模拟器或已连接设备上测试或操作 Android 应用或 Expo 项目:检查界面、驱动 UI、确认预期元素是否出现。适用于本地开发和测试流程,而非日常手机使用。
运行要求
通过 npm(Node 18+)或一键桌面安装包在本地运行。需要可用的 Android SDK platform-tools(adb),并连接模拟器或设备。可选环境变量:ADB_PATH、ADB_SERIAL、ADB_TIMEOUT_MS、ADB_MAX_BUFFER_MB、ADB_DEBUG、MCP_TRANSPORT 和 PORT。未声明认证。
安装前请注意
点击、滑动、输入、发送按键、启动应用或安装 APK 的工具会改变所连设备的状态;README 说明客户端可利用声明的注解限制这些操作。installExpoGo 会从互联网下载 APK 并用 adb install -r 安装。将 MCP_TRANSPORT 设为 http 或 both 会开放本地 HTTP 端口(默认 7332),且未声明认证。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Expo Android MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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:

bash
adb devices

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:

bash
npm install -g @fndchagas/expo-android# ornpx -y @fndchagas/expo-android

Quickstart

  1. Start an emulator or connect a device.
  2. Run doctor to validate adb + device selection.
  3. Use inspect, tapElement, inputText, etc.

Example:

ts
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

bash
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

bash
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:

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

VariableDefaultDescription
ADB_PATHadbPath to adb executable
ADB_SERIALoptionalDevice serial to target (auto to clear and auto-detect)
ADB_TIMEOUT_MS15000Timeout for adb commands
ADB_MAX_BUFFER_MB10Max output buffer size
ADB_DEBUG0Log adb diagnostics to stderr
MCP_TRANSPORTstdioTransport: stdio, http, or both
PORT7332HTTP 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:

bash
export ADB_PATH="$HOME/Library/Android/sdk/platform-tools/adb"# orexport 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:

ts
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

bash
npm run buildnpm test

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 via adb install -r (the url override only accepts official github.com/expo/expo-go-releases URLs).

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, textContains
  • contentDesc, contentDescContains
  • resourceId, resourceIdContains
  • class
  • normalizeWhitespace, caseInsensitive

MCP usage examples

Inspect

ts
const result = await client.callTool({  name: 'expo-android.inspect',  arguments: { onlyInteractive: true, includeScreenshot: false, maxElements: 200 },});

Inspect options:

  • includeScreenshot (default: false)
  • screenshotMode: base64 or path
  • screenshotPath: optional file path when using path
  • maxElements: limit elements returned
  • includeElements: return elements or summary only

Doctor

ts
await client.callTool({  name: 'expo-android.doctor',  arguments: {},});

Override serial per call

ts
await client.callTool({  name: 'expo-android.tapElement',  arguments: { text: 'Search', serial: 'emulator-5554' },});

Tap element

ts
await client.callTool({  name: 'expo-android.tapElement',  arguments: { text: 'Private account' },});

Wait + assert

ts
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 },});

来源:README.md,提交 11bf4d0

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.5.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分