Expo Android MCP
Let your coding agent drive an Android emulator through ADB so you can test Expo and React Native flows without leaving the chat.
Overview
Expo Android MCP is a MCP server for the Build phase that automates Android emulators through ADB so agents can run device actions during Expo and React Native development.
What is this MCP server?
- Stdio MCP transport with optional HTTP on port 7332 for local or dual-mode setups
- Configurable ADB path, serial targeting, 15s default command timeout, and 10 MB output buffer
- Published on npm as @fndchagas/expo-android (server schema v0.2.1)
- Environment knobs for ADB_DEBUG and MCP_TRANSPORT (stdio, http, or both)
- Targets Expo and React Native workflows that already rely on Android emulators
- Server package version 0.2.1 on npm as @fndchagas/expo-android
- Default ADB command timeout 15000 ms and max output buffer 10 MB
- Optional HTTP transport default port 7332 when MCP_TRANSPORT includes http
What problem does it solve?
Testing Android builds means juggling adb, emulators, and chat-based agents that cannot see or control the device natively.
Who is it for?
Indie mobile developers using Claude Code or Cursor on Expo/React Native who want hands-free emulator checks during feature work.
Skip if: Teams that only ship iOS, use cloud device farms exclusively, or do not run MCP in their agent stack.
What do I get? / Deliverables
After you register the server, your agent can execute ADB-backed emulator steps as MCP tools while you keep coding in the same session.
- MCP tools that proxy ADB commands against your chosen emulator serial
- Repeatable agent-driven device actions during local Android test loops
- Configurable timeouts and buffers for safer long-running adb output
Recommended MCP Servers
Journey fit
Emulator automation sits in Build because you use it while implementing and verifying mobile UI and native bridges, not during initial idea research or post-launch growth. Agent-tooling is the right shelf: the server exposes device control as MCP tools so Claude Code, Cursor, or Codex can tap, scroll, install builds, and read logs on your behalf.
How it compares
ADB-backed MCP integration for mobile dev, not a hosted Expo build service or a generic browser automation skill.
Common Questions / FAQ
Who is Expo Android MCP for?
Solo and indie builders on Expo or React Native who want their AI agent to operate Android emulators via MCP instead of manual adb typing.
When should I use Expo Android MCP?
Use it during Build when you need repeatable emulator taps, installs, or log reads while iterating on Android-specific behavior alongside your agent.
How do I add Expo Android MCP to my agent?
Install @fndchagas/expo-android from npm, set ADB_PATH (and optional ADB_SERIAL), add the stdio server entry to your MCP config, and ensure an emulator is running.