In-depth architectural comparison of the MCP Linux Tools and Agent Droid Bridge MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Linux Tools
OS Automation · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Agent Droid Bridge
OS Automation · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Linux Tools if you need specialized OS Automation tools running via a hosted cloud SSE transport. Choose Agent Droid Bridge if your workspace requires OS Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Linux Tools when:
You need dedicated capabilities in the OS Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Allowlisted directories, services, and WordPress sites, File listing, reading, and log head/tail operations, Systemd status, reload, and restart controls.
Administer a Linux server from an MCP client such as Cursor or VS Code: read files and tail logs, check/reload/restart systemd services, manage cron jobs inside a dedicated crontab section, run read-only MySQL queries, drive WP-CLI on WordPress sites, run safe Git commands, and execute sandboxed Python. Directories, services and WordPress sites are allowlisted in config.json, and every tool returns a uniform {success, data, error, meta} response. Runs as a systemd service over HTTP.
MCP server giving AI agents programmatic control over Android devices and emulators via ADB. 11 tools covering UI inspection, screen interaction, ADB commands, and change detection.
Tools & Capabilities Breakdown
MCP Linux Tools Tools (6)
Allowlisted directories, services, and WordPress sites
File listing, reading, and log head/tail operations
Systemd status, reload, and restart controls
Cron job listing and management
Read-only MySQL queries with blocked dangerous queries
Sandboxed Python execution with no network and an 8-second timeout
Agent Droid Bridge Tools (14)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Linux Tools is categorized under OS Automation and uses a remote streaming HTTP/SSE transport. In contrast, Agent Droid Bridge belongs to OS Automation using local stdio subprocess. Select MCP Linux Tools when you need capabilities focused on os automation and Agent Droid Bridge when you require tools for os automation.
Returns 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_screen
A tap gesture at the given pixel coordinates on the Android screen.
swipe_screen
A swipe gesture on the Android screen from (x1,y1) to (x2,y2) over the given duration.
type_text
Text input into the currently focused Android input field.
Spaces are encoded automatically.
press_key
A key event sent to the Android device using the given keycode integer.
take_screenshot
A PNG screenshot of the current Android device screen with width, height,
and base64-encoded image data.
list_devices
All Android devices currently visible to ADB, with their serial numbers,
connection state, and model names.
launch_app
An Android app launched by its component name (package/activity).
execute_adb_command
The output of an ADB command. Parsed safely via shlex and never passed to a system shell.
snapshot_ui
Takes 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_change
Polls 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_elements
Structured 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.