Device Manager MCP server

Read from the package source without running it. The installed server may list more.

• device_backend_status

  Get the current backend status showing whether scrcpy (fast) or adb (fallback) is being used.

• device_list

  List all connected Android devices.

• device_press_key

  Press a key on the device (e.g., BACK, HOME, ENTER).

• device_screen_size

  Get the screen size of the device in pixels.

• device_screenshot

  Take a screenshot of the device screen. Returns base64-encoded PNG image. Uses scrcpy for ~40ms latency when available, falls back to adb (~500ms).

• device_swipe

  Swipe on the screen from start to end coordinates.

• device_tap

  Tap on the screen at the specified coordinates. Uses scrcpy for ~50ms latency when available.

• device_type

  Type text on the device.

• Code scan9 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Device Manager: common questions

Is Device Manager MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Device Manager safety report

How do I install Device Manager?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Device Manager need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Device Manager maintained?

The latest release is v1.0.7.

What can I use instead of Device Manager?

Servers from other publishers that do the same job: MCP Appium - Mobile Development and Automation Server MCP server.