Agent Droid Bridge vs Oswright
A side-by-side look at the Agent Droid Bridge and Oswright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Droid Bridge for os automation work as a local process; choose Oswright 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 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.
Choose Oswright when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
screenshot, get_screen_info, find_text_on_screen.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ADB_EXECUTION_MODEADB_ALLOW_SHELLADB_PATHADB_EXTRA_TOOL_PACKSMCP_LOG_ENABLEDMCP_LOG_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 22 | 4 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 14 | 43 |
| Full listing | View Agent Droid Bridge | View Oswright |
Tools & capabilities
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
Oswright tools 43
screenshotTake a screenshot of the screen or a region. Returns the image as native MCP image content. Optionally saves to a file path. Args: save_path: Optional file path to save the screenshot. region_left: Left coordinate for a sub-region capture. region_top: Top coordinate for a sub-region capture. region_width: Width of the sub-region. region_height: Height of the sub-region. monitor: Monitor index (0 = all monitors, 1 = primary, etc.).get_screen_infoGet screen dimensions and monitor count. Args: monitor: Monitor index (0 = all monitors combined).find_text_on_screenFind all occurrences of text on screen using OCR. Returns a list of matches with coordinates and confidence. Coordinates are absolute screen coordinates, ready to pass straight to mouse_click. Args: text: The text to search for on screen. exact: If True, requires exact match. If False, substring match. region_left: Optional left bound to restrict search area. region_top: Optional top bound to restrict search area. region_width: Optional width to restrict search area. region_height: Optional height to restrict search area. monitor: Monitor index.read_screen_textRead ALL visible text on the screen using OCR. Returns every detected text element with its position, in absolute screen coordinates that are ready to click. Args: region_left: Optional left bound to restrict OCR area. region_top: Optional top bound to restrict OCR area. region_width: Optional width to restrict OCR area. region_height: Optional height to restrict OCR area. monitor: Monitor index.find_image_on_screenFind all occurrences of a template image on screen. Coordinates are absolute screen coordinates, ready to pass to mouse_click. Args: template_path: Absolute path to the template image file to find. threshold: Minimum match confidence (0.0-1.0, default 0.8). monitor: Monitor index.mouse_clickClick the mouse at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. If not provided, clicks at current position. y: Y screen coordinate. If not provided, clicks at current position. button: Mouse button - 'left', 'right', or 'middle'. clicks: Number of clicks (2 for double-click).mouse_double_clickDouble-click at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. y: Y screen coordinate.mouse_moveMove the mouse cursor to screen coordinates. Args: x: X screen coordinate. y: Y screen coordinate.mouse_scrollScroll the mouse wheel. Returns action result and a screenshot of current screen state. Args: amount: Scroll amount. Positive = up, negative = down. x: Optional X coordinate to scroll at. y: Optional Y coordinate to scroll at.mouse_dragDrag from one point to another. Returns action result and a screenshot of current screen state. Args: start_x: Starting X coordinate. start_y: Starting Y coordinate. end_x: Ending X coordinate. end_y: Ending Y coordinate. button: Mouse button to hold ('left' or 'right'). duration: Duration of the drag in seconds.get_mouse_positionGet the current mouse cursor position.type_textType text using the keyboard (character by character). Returns action result and a screenshot of current screen state. Args: text: The text to type. delay: Delay in seconds between each character.- +31 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.
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"
}
}
}
}
Oswright
{
"mcpServers": {
"oswright": {
"command": "uvx",
"args": [
"oswright"
]
}
}
}
Frequently asked questions
Agent Droid Bridge is categorized under OS Automation and uses a local stdio subprocess. Oswright belongs to OS Automation and uses a local stdio subprocess. Pick Agent Droid Bridge for os automation work and Oswright 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.
Agent Droid Bridge is listed as free. Auth: no auth required. Oswright 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 neverlow512-agent-droid-bridge and oswright as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Droid Bridge has a quality signal of 57/100 (Good) with 3 views, 0 installs and 22 GitHub stars. Oswright has 59/100 (Good) with 2 views, 0 installs and 4 GitHub stars.