ERIUS PHONE vs Agent Droid Bridge
A side-by-side look at the ERIUS PHONE and Agent Droid Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ERIUS PHONE for os automation work as a local process; choose Agent Droid Bridge 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 ERIUS PHONE when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ERIUS_PHONE_API_KEY, ERIUS_PHONE_DEFAULT_DEVICE, ERIUS_PHONE_API_URL, ERIUS_PHONE_TIMEOUT. - You want tools like
list_devices, whoami, get_device.
Choose Agent Droid Bridge when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ADB_EXECUTION_MODE, ADB_ALLOW_SHELL, ADB_PATH, ADB_EXTRA_TOOL_PACKS, MCP_LOG_ENABLED, MCP_LOG_DIR. - You want tools like
get_ui_hierarchy, tap_screen, swipe_screen.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 60/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | ERIUS_PHONE_API_KEYERIUS_PHONE_DEFAULT_DEVICEERIUS_PHONE_API_URLERIUS_PHONE_TIMEOUT | ADB_EXECUTION_MODEADB_ALLOW_SHELLADB_PATHADB_EXTRA_TOOL_PACKSMCP_LOG_ENABLEDMCP_LOG_DIR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 22 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 21 | 14 |
| Full listing | View ERIUS PHONE | View Agent Droid Bridge |
Tools & capabilities
ERIUS PHONE tools 21
list_devicesList every Android device your API key can access, with live status (booted, Android version, screen size). Call this first to get device ids.whoamiShow which ERIUS PHONE account (tenant) and key id this server is using, and the device ids it can access. Handy to check the API key works.get_deviceGet full status of one device: boot state, Android version, screen size, and the app currently in the foreground. Omit `device` to use the default.snapshotGet an accessibility-tree snapshot of the current screen: every visible element with its text, role, and a `ref` id you can pass to tap/type/scroll. This is how the agent 'sees' the phone — read it before acting, and take a fresh one after any action since refs reset on every snapshot.screenshotTake a screenshot of the device screen right now and return it as an image you can look at, plus one line of text with the image size and the device's real screen size. The default is a JPEG whose longest side is 1024 px (tens of KB). A full-size PNG of a 1440x3120 phone is about 3 MB, which is more than many MCP clients accept in a tool result, so ask for it only when you need it: format="png", max_side=None. `format` is "jpeg", "webp" or "png"; `quality` is 1-100 (jpeg/webp); `max_side` caps the longest side in pixels (64-8192); `scale` (0.1-1) shrinks by a factor instead. When the image is smaller than the screen, pass its size as image_width/image_height to tap(), long_press() or swipe() so x,y are read in the image's pixels. Prefer snapshot() when you only need text and refs: it's far smaller.foregroundGet just the foreground app: package, activity, and whether a crash dialog is showing. Cheaper than a full snapshot when you only need this.tapTap an element. Prefer `ref` from a snapshot(), or `text`/`content_desc` to tap by visible label. Falls back to raw `x`,`y` pixel coordinates: in device pixels, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size (the API maps the point to the screen).long_pressLong-press an element (e.g. to open a context menu or start a drag). Targets work like tap(): `ref`, `text`/`content_desc`, or raw `x`,`y` (with `image_width`/`image_height` when they come from a scaled screenshot). `ms` (hold time, default 800) only applies to the x,y form.type_textType text into a field. Optionally tap a `ref` or `text_target` label first to focus the field, `clear` the existing value, or press Enter after. Keystrokes sent while the field is still opening are lost, so if tapping the field opens a new screen (e.g. a search page), tap it first, wait for it with snapshot() or wait_for_text(), then type with no target. Check the result with snapshot(). Only printable ASCII is supported (adb limitation).press_keyPress a hardware/navigation key: back, home, enter, delete, tab, escape, up, down, left, right, space, power, volup, voldown, recent, menu, wakeup.swipeSwipe from one point to another: in device pixel coordinates, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size.scrollScroll a list/container up, down, left, or right. `ref` must be the ref of the scrollable container itself (a ScrollView or List line in the snapshot), not of a row inside it: scrolling a single row does nothing. If the container has no ref, use swipe() instead.- +9 more on the listing page
Agent Droid Bridge tools 14
get_ui_hierarchyReturns the current Android screen as an XML UI hierarchy. Use this when you need to locate element coordinates, read text, or find resource IDs to interact with. Do not call this after every action — only call it when you actually need to read screen content. To check if the screen changed after an action, use snapshot_ui before the action and detect_ui_change after.tap_screenA tap gesture at the given pixel coordinates on the Android screen.swipe_screenA swipe gesture on the Android screen from (x1,y1) to (x2,y2) over the given duration.type_textText input into the currently focused Android input field. Spaces are encoded automatically.press_keyA key event sent to the Android device using the given keycode integer.take_screenshotA PNG screenshot of the current Android device screen with width, height, and base64-encoded image data.list_devicesAll Android devices currently visible to ADB, with their serial numbers, connection state, and model names.launch_appAn Android app launched by its component name (package/activity).execute_adb_commandThe output of an ADB command. Parsed safely via shlex and never passed to a system shell.snapshot_uiTakes a lightweight snapshot of the current UI state and returns a short token. Use this before performing an action (tap, swipe, launch, key press) when you only need to confirm the screen changed afterward — not read its content. Pass the returned token to detect_ui_change as baseline_token. This avoids loading the full XML hierarchy into context unnecessarily. Do not use this when you need to read or interact with screen elements — use get_ui_hierarchy for that.detect_ui_changePolls the UI hierarchy after an action and returns when the screen content changes or the timeout is reached. Returns changed status and elapsed time. By default, omits the XML hierarchy for efficiency — set return_hierarchy=True to receive the full hierarchy. For efficient change detection: call snapshot_ui before the action, perform the action, then call detect_ui_change with baseline_token. Only use without baseline_token when you need to wait for a slow transition (loading screens, animations). Do not use to read the current screen state — use get_ui_hierarchy for that.get_screen_elementsStructured list of UI elements currently visible on the Android screen. Returns elements filtered and shaped by the chosen mode. Prefer 'tappable' for navigation and 'interactive' when you need XPath or bounds for ADB commands. Only use 'all' as a last resort — it returns every node and can be large.- +2 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.
ERIUS PHONE
{
"mcpServers": {
"erius-phone": {
"command": "uvx",
"args": [
"erius-phone-mcp"
],
"env": {
"ERIUS_PHONE_API_KEY": "YOUR_ERIUS_PHONE_API_KEY_HERE",
"ERIUS_PHONE_DEFAULT_DEVICE": "YOUR_ERIUS_PHONE_DEFAULT_DEVICE_HERE",
"ERIUS_PHONE_API_URL": "YOUR_ERIUS_PHONE_API_URL_HERE",
"ERIUS_PHONE_TIMEOUT": "YOUR_ERIUS_PHONE_TIMEOUT_HERE"
}
}
}
}
Agent Droid Bridge
{
"mcpServers": {
"neverlow512-agent-droid-bridge": {
"command": "uvx",
"args": [
"agent-droid-bridge"
],
"env": {
"ADB_EXECUTION_MODE": "YOUR_ADB_EXECUTION_MODE_HERE",
"ADB_ALLOW_SHELL": "YOUR_ADB_ALLOW_SHELL_HERE",
"ADB_PATH": "YOUR_ADB_PATH_HERE",
"ADB_EXTRA_TOOL_PACKS": "YOUR_ADB_EXTRA_TOOL_PACKS_HERE",
"MCP_LOG_ENABLED": "YOUR_MCP_LOG_ENABLED_HERE",
"MCP_LOG_DIR": "YOUR_MCP_LOG_DIR_HERE"
}
}
}
}
Frequently asked questions
ERIUS PHONE is categorized under OS Automation and uses a local stdio subprocess. Agent Droid Bridge belongs to OS Automation and uses a local stdio subprocess. Pick ERIUS PHONE for os automation work and Agent Droid Bridge 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.
ERIUS PHONE has no declared pricing — check the project's own site. Agent Droid Bridge is listed as free. Auth: no auth required. 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 erius-phone and neverlow512-agent-droid-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ERIUS PHONE has a quality signal of 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Agent Droid Bridge has 57/100 (Good) with 3 views, 0 installs and 22 GitHub stars.