Droidsight vs Agent Device
A side-by-side look at the Droidsight and Agent Device MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Droidsight for os automation work as a local process; choose Agent Device for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Droidsight when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DROIDSIGHT_DEVICE_SERIAL, DROIDSIGHT_ADB_PATH, DROIDSIGHT_LOCAL_ROOT, DROIDSIGHT_DEVICE_PIN, DROIDSIGHT_ALLOW_SHELL, DROIDSIGHT_DEBUG_LOG. - You want tools like
mcp_android_vision_query, mcp_android_vision_stream, mcp_android_get_view_hierarchy.
Choose Agent Device when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 56/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | DROIDSIGHT_DEVICE_SERIALDROIDSIGHT_ADB_PATHDROIDSIGHT_LOCAL_ROOTDROIDSIGHT_DEVICE_PINDROIDSIGHT_ALLOW_SHELLDROIDSIGHT_DEBUG_LOG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 5,133 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 31 | Not listed |
| Full listing | View Droidsight | View Agent Device |
Tools & capabilities
Droidsight tools 31
mcp_android_vision_queryScreenshot, hierarchy, OCR, and element or template search. Its `elements` and `tap_element` actions avoid coordinate arithmetic entirely.mcp_android_vision_streamStart, stop, or read the background H.264 stream.mcp_android_get_view_hierarchyThe accessibility tree as structured JSON.mcp_android_smart_waitBlock until an element appears, or time out.mcp_android_input_actTap, type, key events, swipe, smart tap, and IME control.mcp_android_tap_textScan for text and tap it the instant it appears, retrying until timeout. Avoids the miss between a screenshot and a tap.mcp_android_run_flowRun a bounded, fully prevalidated sequence of safe actions.mcp_android_record_gestureRecord raw touch input for a fixed duration.mcp_android_play_gestureReplay a recorded gesture timeline.mcp_android_app_manageLaunch, stop, list, install, and read crash logs. Uninstall, clear data, permission, enable, and disable additionally require `confirm_destructive`.mcp_android_app_instrumentationDeep state inspection: activity, window, process list, stack traces.mcp_android_open_urlOpen a URL.- +19 more on the listing page
Agent Device tools
No tool names declared yet. Check the project README from 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.
Droidsight
{
"mcpServers": {
"droidsight": {
"command": "npx",
"args": [
"-y",
"@edgecasehuman/droidsight"
],
"env": {
"DROIDSIGHT_DEVICE_SERIAL": "YOUR_DROIDSIGHT_DEVICE_SERIAL_HERE",
"DROIDSIGHT_ADB_PATH": "YOUR_DROIDSIGHT_ADB_PATH_HERE",
"DROIDSIGHT_LOCAL_ROOT": "YOUR_DROIDSIGHT_LOCAL_ROOT_HERE",
"DROIDSIGHT_DEVICE_PIN": "YOUR_DROIDSIGHT_DEVICE_PIN_HERE",
"DROIDSIGHT_ALLOW_SHELL": "YOUR_DROIDSIGHT_ALLOW_SHELL_HERE",
"DROIDSIGHT_DEBUG_LOG": "YOUR_DROIDSIGHT_DEBUG_LOG_HERE"
}
}
}
}
Agent Device
No confirmed install command for Agent Device yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Droidsight is categorized under OS Automation and uses a local stdio subprocess. Agent Device belongs to OS Automation and uses an install path we have not confirmed yet. Pick Droidsight for os automation work and Agent Device 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 Device has no confirmed install command yet — follow its own setup instructions.
Droidsight has no declared pricing — check the project's own site. Agent Device 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 droidsight and agent-device as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Droidsight has a quality signal of 56/100 (Good) with 2 views, 0 installs and 4 GitHub stars. Agent Device has 45/100 (Fair) with 5 views, 0 installs and 5,133 GitHub stars.