Adb MCP Server

MCP server for Android Debug Bridge (ADB) interactions in TypeScript

Local serverstdioTypeScript

What is the Adb MCP MCP server?

MCP server for Android Debug Bridge (ADB) interactions in TypeScript. Exposed over MCP by the adb mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

I've been working on something that is faster, more scalable and also works with iOS, take a look at mobile-device-mcp.

  • 📱 Device Management - List and interact with connected Android devices
  • 📦 App Installation - Deploy APK files to connected devices
  • 📋 Logging - Access device logs through logcat
  • 🔄 File Transfer - Push and pull files between device and host
  • 📸 UI Interaction - Capture screenshots and analyze UI hierarchy
  • 🔧 Shell Command Execution - Run custom commands on the device

Configuration

You will need one environment variable: ADB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js (v16 or higher recommended, tested with Node.js v16, v18, and v20) - ADB (Android Debug Bridge) installed and in your PATH - An Android device or emulator connected via USB or network with USB debugging enabled - Permission to access the device (accepted debugging authorization on device)

Adding it to your client

The server ships on npm as @smithery/cli, 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.

When to reach for it

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by srmorete; 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.

Caveats

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the adb mcp mcp server does with a few real requests.

How to install the Adb MCP MCP server

{
  "mcpServers": {
    "adb": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "ADB_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js (v16 or higher recommended, tested with Node.js v16, v18, and v20) - ADB (Android Debug Bridge) installed and in your PATH - An Android device or emulator connected via USB or network with USB debugging enabled - Permission to access the device (accepted debugging authorization on device)
VariableDescriptionRequired
ADB_PATHFilesystem location the server is allowed to use.Optional

Frequently asked questions

It connects Adb MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Adb MCP directly.