Native Devtools MCP Server

There's also a fourth, niche path: **AppDebugKit** (`app_connect` / `app_query` / `app_click`) for apps instrumented with the AppDebugKit library.

Remote serverstreamable-httpGo

What is the Native Devtools MCP MCP server?

Connect Native Devtools MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. There's also a fourth, niche path: AppDebugKit (app_connect / app_query / app_click) for apps instrumented with the AppDebugKit library. Mostly useful for developers testing their own apps. The native devtools mcp mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • android_list_devices — List all ADB-connected devices (always available)
  • android_connect — Connect to a device by serial number
  • android_disconnect — Disconnect from the current device
  • android_screenshot — Capture the device screen
  • android_find_text — Find UI elements by text (via uiautomator)
  • android_click — Tap at screen coordinates
  • android_swipe — Swipe between two points
  • android_type_text — Type text on the device
  • android_press_key — Press a key (e.g., KEYCODE_HOME, KEYCODE_BACK)
  • android_launch_app — Launch an app by package name
  • android_list_apps — List installed packages
  • android_get_display_info — Get screen resolution and density

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

  1. ADB installed on the host (brew install android-platform-tools on macOS, or via Android SDK). 2. USB debugging enabled on the device (Settings > Developer options > USB debugging). 3. ADB server running — starts automatically when you run adb devices.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Native Devtools MCP's toolset — android_list_devices, android_connect, android_disconnect and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sh3ll3x3c; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Native Devtools MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Native Devtools MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
android_list_devicesList all ADB-connected devices (always available)
android_connectConnect to a device by serial number
android_disconnectDisconnect from the current device
android_screenshotCapture the device screen
android_find_textFind UI elements by text (via uiautomator)
android_clickTap at screen coordinates
android_swipeSwipe between two points
android_type_textType text on the device
android_press_keyPress a key (e.g., KEYCODE_HOME, KEYCODE_BACK)
android_launch_appLaunch an app by package name
android_list_appsList installed packages
android_get_display_infoGet screen resolution and density
android_get_current_activityGet the current foreground activity
Prerequisites1. **ADB installed** on the host (brew install android-platform-tools on macOS, or via [Android SDK](https://developer.android.com/tools/releases/platform-tools)). 2. **USB debugging enabled** on the device (Settings > D

How to install the Native Devtools MCP MCP server

{
  "mcpServers": {
    "native-devtools": {
      "command": "/Applications/NativeDevtools.app/Contents/MacOS/native-devtools-mcp"
    }
  }
}

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

Configuration

  1. ADB installed on the host (brew install android-platform-tools on macOS, or via Android SDK). 2. USB debugging enabled on the device (Settings > Developer options > USB debugging). 3. ADB server running — starts automatically when you run adb devices.

Example prompts to try

  • Use Native Devtools MCP to android list devices.
  • Use Native Devtools MCP to android connect.
  • Use Native Devtools MCP to android disconnect.

Frequently asked questions

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