Dittu vs Agent Droid Bridge
A side-by-side look at the Dittu 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 Dittu for os automation work over a hosted endpoint; 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 Dittu when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
take_screenshot, take_screenshot_with_grid, take_screenshot_with_crosshair.
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 | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | ADB_EXECUTION_MODEADB_ALLOW_SHELLADB_PATHADB_EXTRA_TOOL_PACKSMCP_LOG_ENABLEDMCP_LOG_DIR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 22 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 12 | 14 |
| Full listing | View Dittu | View Agent Droid Bridge |
Tools & capabilities
Dittu tools 12
take_screenshotCapture the current screen via the Dittu phone camera. Returns a JPEG image. Call this to see what's on screen before acting.take_screenshot_with_gridCapture the screen and overlay a coordinate grid. step: grid spacing (default 0.1, use 0.05 for finer grid on small UI elements). Returns a JPEG image with grid drawn on top.take_screenshot_with_crosshairCapture the screen, crop tightly around (nx, ny), zoom in, and draw a crosshair at exactly that expected position. Use this for screen-corner calibration: move_mouse(nx, ny) near a screen edge, then call this to see whether the actual cursor lines up with the crosshair (where it SHOULD be if calibration is perfect). If the cursor is offset from the crosshair, or missing entirely (edge is cropped out of frame), corners need adjusting — see get_corners/set_corners. nx, ny: the same coordinates you passed to move_mouse. zoom: magnification factor for the cropped region (default 4x).get_raw_screenshotCapture the RAW camera frame — no perspective warp, no crop to the calibrated screen quad. Use this to see exactly what the camera sees before any correction, e.g. when troubleshooting why take_screenshot looks wrong, or before adjusting corners with get_corners/set_corners.get_cornersGet the phone's current screen-corner calibration. Returns {"tl": [nx,ny], "tr": [nx,ny], "br": [nx,ny], "bl": [nx,ny]} — each corner is a normalized point (0.0–1.0) in the RAW camera frame, defining the perspective warp that maps the camera view onto a flat rectangle representing the monitor. These four points are an arbitrary quadrilateral (trapezoid), not a bounding box — adjust one corner at a time without assuming the others move symmetrically.set_cornersUpdate the phone's screen-corner calibration. Each corner is [nx, ny] normalized 0.0–1.0 in the raw camera frame. tl/tr/br/bl = top-left/top-right/bottom-right/bottom-left of the monitor as seen by the camera (an arbitrary trapezoid due to perspective — not a rectangle). Call get_corners() first to read the current values before nudging one of them.move_mouseMove mouse cursor to normalized coordinates WITHOUT clicking. nx, ny: float 0.0000–1.0000.clickClick at normalized screen coordinates. nx, ny: float 0.0000–1.0000 where (0,0) = top-left, (1,1) = bottom-right.double_clickDouble-click at normalized screen coordinates.type_textType text on the computer keyboard.keyPress a key combination. modifiers bitmask: LCtrl=1, LShift=2, LAlt=4, LWin=8 Common keycodes: Enter=40, Escape=41, Tab=43, Space=44, F4=61, PageDown=78, PageUp=75, Win=227 Examples: Alt+F4 → key(4, [61]) Ctrl+W → key(1, [26])scrollScroll the mouse wheel. delta: number of ticks. Positive = scroll down, negative = scroll up.
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.
Dittu
{
"mcpServers": {
"dittu": {
"url": "https://app.dittu.org/mcp"
}
}
}
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
Dittu is categorized under OS Automation and uses a remote HTTP/SSE transport. Agent Droid Bridge belongs to OS Automation and uses a local stdio subprocess. Pick Dittu 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.
Dittu 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 dittu and neverlow512-agent-droid-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dittu has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Agent Droid Bridge has 57/100 (Good) with 3 views, 0 installs and 22 GitHub stars.