Mobile Device MCP Server

MCP server that gives AI coding assistants (Claude, Cursor, Windsurf) the ability to see and interact with Android mobile devices via ADB —

Local serverstdioPython

What is the Mobile Device MCP MCP server?

Mobile Device MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server that gives AI coding assistants (Claude, Cursor, Windsurf) the ability to see and interact with Android mobile devices via ADB — AI-powered visual inspection, element finding, and device automation.

What the assistant can call

Once Mobile Device MCP is connected, these are the calls the assistant has available:

  • list_devices — List all connected Android devices/emulators
  • get_device_info — Model, manufacturer, Android version, SDK level
  • get_screen_size — Screen resolution in pixels
  • take_screenshot — Capture screenshot (PNG or JPEG, configurable quality & resize)
  • get_ui_elements — Get the accessibility/UI element tree as structured JSON
  • tap — Tap at coordinates
  • double_tap — Double tap at coordinates
  • long_press — Long press at coordinates
  • swipe — Swipe between two points
  • type_text — Type text into the focused field
  • press_key — Press a key (home, back, enter, volume, etc.)
  • list_apps — List installed apps

Configuration and credentials

You will need 5 environment variables: GOOGLE_API_KEY, MOBILE_MCP_LICENSE_KEY, GEMINI_API_KEY, ANTHROPIC_API_KEY, MCP_ADB_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at mobile-device-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mobile Device MCP's toolset — list_devices, get_device_info, get_screen_size and 11 more — is a fair guide to whether it matches your workflow. It is maintained by saranshbamania; worth a glance at recent repository activity before you build anything load-bearing on it.

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

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 Mobile Device MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mobile device mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
list_devicesList all connected Android devices/emulators
get_device_infoModel, manufacturer, Android version, SDK level
get_screen_sizeScreen resolution in pixels
take_screenshotCapture screenshot (PNG or JPEG, configurable quality & resize)
get_ui_elementsGet the accessibility/UI element tree as structured JSON
tapTap at coordinates
double_tapDouble tap at coordinates
long_pressLong press at coordinates
swipeSwipe between two points
type_textType text into the focused field
press_keyPress a key (home, back, enter, volume, etc.)
list_appsList installed apps
get_current_appGet the foreground app
get_logsGet logcat entries with filtering

How to install the Mobile Device MCP MCP server

**Windows:**
```json
{
  "mcpServers": {
    "mobile-device": {
      "type": "stdio",
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mobile-device-mcp"],
      "env": {
        "GOOGLE_API_KEY": "your-google-api-key"
      }
    }
  }
}

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

Configuration

VariableDescriptionRequired
GOOGLE_API_KEYCredential the server authenticates with.Yes
MOBILE_MCP_LICENSE_KEYCredential the server authenticates with.Yes
GEMINI_API_KEYCredential the server authenticates with.Yes
ANTHROPIC_API_KEYCredential the server authenticates with.Yes
MCP_ADB_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Mobile Device MCP to list devices.
  • Use Mobile Device MCP to get device info.
  • Use Mobile Device MCP to get screen size.

Frequently asked questions

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