Deepadb MCP Server

DeepADB — full-featured Android Debug Bridge MCP server. 204 tools across 45 modules for device inspection from UI to baseband.

Local serverstdio

What is the Deepadb MCP server?

Deepadb MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. DeepADB — full-featured Android Debug Bridge MCP server. 204 tools across 45 modules for device inspection from UI to baseband.

What you get

MCP (Model Context Protocol) server providing full Android Debug Bridge (ADB) integration for AI agents. Enables MCP clients to directly interact with connected Android devices — inspecting state, running commands, managing apps, capturing logs, controlling device settings, analyzing UI hierarchies, recording screens, managing emulators, running structured test sessions, orchestrating multi-device operations, capturing network traffic, running CI pipelines, auditing accessibility, detecting performance regressions, executing cloud device farm tests, debugging over WiFi, building projects, and managing community

What the assistant can call

Once Deepadb is connected, these are the calls the assistant has available:

  • adb_devices — List all connected devices with state, model, and product info
  • adb_device_info — Detailed device properties (model, OS, SDK, build, security patch, ABI)
  • adb_getprop — Read a specific system property or dump all properties
  • adb_shell — Execute arbitrary shell commands with configurable timeout (security-checked)
  • adb_root_shell — Execute commands as root via su (requires rooted device, security-checked)
  • adb_install — Install APK with replace/downgrade options
  • adb_uninstall — Remove package with optional data retention
  • adb_list_packages — List packages filtered by name or type (all/system/third-party)
  • adb_package_info — Detailed package info (version, permissions, paths)
  • adb_clear_data — Clear all app data and cache
  • adb_grant_permission — Grant a runtime permission to a package
  • adb_revoke_permission — Revoke a runtime permission from a package (reset permission state for testing denial flows)

Setting it up

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Deepadb's toolset — adb_devices, adb_device_info, adb_getprop and 11 more — is a fair guide to whether it matches your workflow. It is maintained by fullread; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Deepadb.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the deepadb mcp server does with a few real requests.

Available tools

ToolWhat it does
adb_devicesList all connected devices with state, model, and product info
adb_device_infoDetailed device properties (model, OS, SDK, build, security patch, ABI)
adb_getpropRead a specific system property or dump all properties
adb_shellExecute arbitrary shell commands with configurable timeout (security-checked)
adb_root_shellExecute commands as root via su (requires rooted device, security-checked)
adb_installInstall APK with replace/downgrade options
adb_uninstallRemove package with optional data retention
adb_list_packagesList packages filtered by name or type (all/system/third-party)
adb_package_infoDetailed package info (version, permissions, paths)
adb_clear_dataClear all app data and cache
adb_grant_permissionGrant a runtime permission to a package
adb_revoke_permissionRevoke a runtime permission from a package (reset permission state for testing denial flows)
adb_list_permissionsList all declared and granted permissions for a package, filterable by granted/denied
adb_force_stopForce-stop an app immediately

How to install the Deepadb MCP server

{
  "mcpServers": {
    "deepadb": {
      "command": "node",
      "args": ["/path/to/DeepADB/build/index.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Deepadb to adb devices.
  • Use Deepadb to adb device info.
  • Use Deepadb to adb getprop.

Frequently asked questions

It connects Deepadb to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (adb_devices, adb_device_info, adb_getprop, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Deepadb directly.