Expo Android MCP

Name: Expo Android MCP
Author: frndchagas

by frndchagasversion 0.5.2i★ –iRuns on your computer

Registry nameio.github.frndchagas/expo-android

Install

Overview

Description from the maker (original English)

MCP server for Android emulator automation via ADB.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: ADB_PATH, ADB_SERIAL, ADB_TIMEOUT_MS, ADB_MAX_BUFFER_MB, ADB_DEBUG, MCP_TRANSPORT, PORT

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "expo-android": {
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ],
      "env": {
        "ADB_PATH": "your-value",
        "ADB_SERIAL": "your-value",
        "ADB_TIMEOUT_MS": "your-value",
        "ADB_MAX_BUFFER_MB": "your-value",
        "ADB_DEBUG": "your-value",
        "MCP_TRANSPORT": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add expo-android --env ADB_PATH=your-value --env ADB_SERIAL=your-value --env ADB_TIMEOUT_MS=your-value --env ADB_MAX_BUFFER_MB=your-value --env ADB_DEBUG=your-value --env MCP_TRANSPORT=your-value --env PORT=your-value -- npx -y @fndchagas/expo-android

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "expo-android": {
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ],
      "env": {
        "ADB_PATH": "your-value",
        "ADB_SERIAL": "your-value",
        "ADB_TIMEOUT_MS": "your-value",
        "ADB_MAX_BUFFER_MB": "your-value",
        "ADB_DEBUG": "your-value",
        "MCP_TRANSPORT": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "expo-android": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@fndchagas/expo-android"
      ],
      "env": {
        "ADB_PATH": "your-value",
        "ADB_SERIAL": "your-value",
        "ADB_TIMEOUT_MS": "your-value",
        "ADB_MAX_BUFFER_MB": "your-value",
        "ADB_DEBUG": "your-value",
        "MCP_TRANSPORT": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ADB_PATH env
Path to adb executable.
ADB_SERIAL env
Device serial to target (optional, use 'auto' to clear and auto-detect).
ADB_TIMEOUT_MS env
Timeout for adb commands in milliseconds.
ADB_MAX_BUFFER_MB env
Max buffer size for adb output in MB.
ADB_DEBUG env
Enable adb debug logs (set to 1).
MCP_TRANSPORT env
Transport: stdio, http, or both.
PORT env
HTTP port when MCP_TRANSPORT is http or both.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account frndchagas, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32725 servers in this category
Published to the registry more recently than 29% of the other 32725 servers in this category
Basic checks equal to or better than 100% of the other 32725 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Expo Android MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Signoff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Signoff

by ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

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-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)

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({

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

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

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({

Override serial per call

await client.callTool({

name: 'expo-android.tapElement', arguments: { text: 'Search', serial: 'emulator-5554' }, });

Tap element

await client.callTool({

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

Expo Android MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Signoff

README from the maker

expo-android

Requirements

Install

or

Quickstart

Use with Claude Code CLI

Use with OpenAI Codex CLI

Environment variables

Troubleshooting

adb not found (spawn adb ENOENT)

or

Tests

Tools

Search criteria

MCP usage examples

Inspect

Doctor

Override serial per call

Tap element

Wait + assert