Is Expo Android free?

Yes, Expo Android is free to use.

How do I install Expo Android?

Expo Android is a local plugin. Install it using npm package: @fndchagas/expo-android and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Expo Android need?

Expo Android requires the following credentials or environment variables: ADB_PATH, ADB_SERIAL, ADB_TIMEOUT_MS, ADB_MAX_BUFFER_MB, ADB_DEBUG, MCP_TRANSPORT, PORT. You can find setup instructions on the server detail page.

What AI apps work with Expo Android?

Expo Android uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Expo Android MCP Server

by Fernando Chagas

Developer ToolsLow Risk8.3Local

Free

MCP server for Android emulator automation via ADB.

About

MCP server for Android emulator automation via ADB.

Security Report

8.3

Low Risk8.3Low Risk

Valid MCP server (2 strong, 1 medium validity signals). 2 known CVEs in dependencies (0 critical, 2 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (3/3 approved).

5 files analyzed · 3 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Path to adb executable.Optional

Environment variable: ADB_PATH

Device serial to target (optional, use 'auto' to clear and auto-detect).Optional

Environment variable: ADB_SERIAL

Timeout for adb commands in milliseconds.Optional

Environment variable: ADB_TIMEOUT_MS

Max buffer size for adb output in MB.Optional

Environment variable: ADB_MAX_BUFFER_MB

Enable adb debug logs (set to 1).Optional

Environment variable: ADB_DEBUG

Transport: stdio, http, or both.Optional

Environment variable: MCP_TRANSPORT

HTTP port when MCP_TRANSPORT is http or both.Optional

Environment variable: PORT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-frndchagas-expo-android": {
      "env": {
        "PORT": "your-port-here",
        "ADB_PATH": "your-adb-path-here",
        "ADB_DEBUG": "your-adb-debug-here",
        "ADB_SERIAL": "your-adb-serial-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "ADB_TIMEOUT_MS": "your-adb-timeout-ms-here",
        "ADB_MAX_BUFFER_MB": "your-adb-max-buffer-mb-here"
      },
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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 doctor to 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, textContains
contentDesc, contentDescContains
resourceId, resourceIdContains
class
normalizeWhitespace, 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: base64 or path
screenshotPath: optional file path when using path
maxElements: limit elements returned
includeElements: 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 },
});