Agent Droid Bridge vs Scrivener MCP

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

Scrivener MCP tools

No tool names declared yet. Check the project README from the listing page.