MCP server for Android emulator automation via ADB.
Connect Expo Android MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Android emulator automation via ADB. The expo android mcp mcp server is what makes that connection.
doctor to validate adb + device selection. 3. Use inspect, tapElement, inputText, etc.@fndchagas/expo-android on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
devices — list connected devices and emulatorsdoctor — validate adb availability and show connected devicessetDevice — override the active device serial for this MCP processinspect — 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 criteriatapElement — find an element and tap its centerwaitForElement — wait until an element appears (optionally with state checks)assertElement — verify element existence and statetap — tap at x/y coordinatesswipe — swipe between coordinateslongPress — press and hold at coordinatesConfiguration is passed through the environment: ADB_PATH, ANDROID_HOME. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Expo Android MCP's toolset — devices, doctor, setDevice and 11 more — is a fair guide to whether it matches your workflow. It is maintained by frndchagas; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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). |
{
"mcpServers": {
"expo-android": {
"command": "npx",
"args": ["-y", "@fndchagas/expo-android"],
"env": {
"ADB_PATH": "your-value",
"ANDROID_HOME": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ADB_PATH | Filesystem location the server is allowed to use. | Optional |
| ANDROID_HOME | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.