ZennoDroid: device in ProjectMaker vs Expo Android MCP
A side-by-side look at the ZennoDroid: device in ProjectMaker and Expo Android MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ZennoDroid: device in ProjectMaker for os automation work; choose Expo Android MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ZennoDroid: device in ProjectMaker when
- You need dedicated capabilities in the OS Automation domain.
Choose Expo Android MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ADB_PATH, ADB_SERIAL, ADB_TIMEOUT_MS, ADB_MAX_BUFFER_MB, ADB_DEBUG, MCP_TRANSPORT, PORT. - You want tools like
devices, doctor, setDevice.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 35/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ADB_PATHADB_SERIALADB_TIMEOUT_MSADB_MAX_BUFFER_MBADB_DEBUGMCP_TRANSPORTPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 17 |
| Full listing | View ZennoDroid: device in ProjectMaker | View Expo Android MCP |
Tools & capabilities
ZennoDroid: device in ProjectMaker tools
No tool names declared yet. Check the project README from the listing page.
Expo Android MCP tools 17
deviceslist connected devices and emulators.doctorvalidate adb availability and show connected devices.setDeviceoverride the active device serial for this MCP process.inspectUI dump parsed into elements with a summary (screenshot optional).screenshotcapture a screenshot only (base64 or file path).findElementreturn elements that match search criteria.tapElementfind an element and tap its center.waitForElementwait until an element appears (optionally with state checks).assertElementverify element existence and state.taptap at x/y coordinates.swipeswipe between coordinates.longPresspress and hold at coordinates.- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ZennoDroid: device in ProjectMaker
No confirmed install command for ZennoDroid: device in ProjectMaker yet — follow the setup steps linked from its listing page rather than a guessed package name.
Expo Android MCP
{
"mcpServers": {
"expo-android-mcp": {
"command": "npx",
"args": [
"-y",
"@fndchagas/expo-android"
],
"env": {
"ADB_PATH": "YOUR_ADB_PATH_HERE",
"ADB_SERIAL": "YOUR_ADB_SERIAL_HERE",
"ADB_TIMEOUT_MS": "YOUR_ADB_TIMEOUT_MS_HERE",
"ADB_MAX_BUFFER_MB": "YOUR_ADB_MAX_BUFFER_MB_HERE",
"ADB_DEBUG": "YOUR_ADB_DEBUG_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
ZennoDroid: device in ProjectMaker is categorized under OS Automation and uses an install path we have not confirmed yet. Expo Android MCP belongs to OS Automation and uses a local stdio subprocess. Pick ZennoDroid: device in ProjectMaker for os automation work and Expo Android MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. ZennoDroid: device in ProjectMaker has no confirmed install command yet — follow its own setup instructions.
ZennoDroid: device in ProjectMaker has no declared pricing — check the project's own site. Expo Android MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add zennodroid-device-in-projectmaker and expo-android-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ZennoDroid: device in ProjectMaker has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Expo Android MCP has 52/100 (Good) with 1 views, 0 installs and 4 GitHub stars.