Skip to main content
Glama

mcp-devices 4.2.0 (ex-claude-in-mobile)

👉 Want everything in one package? Keep using claude-in-mobile.

Nothing changes for you. Same install, all platforms bundled, still maintained:

npm i -g claude-in-mobile

That's it — the all-in-one edition. Read on only if you'd rather install the platforms separately (that's what mcp-devices is for).


Related MCP server: Android MCP Server

Two editions — same tool

Edition

Best for

Install

claude-in-mobile

Want it all in one, zero setup

npm i -g claude-in-mobile

mcp-devices

Want a slim base + only the platforms you need

npm i -g mcp-devices (+ platform plugins, below)

Both are maintained. claude-in-mobile was renamed to mcp-devices in 4.0 and split into a modular edition; the all-in-one keeps its name and its unchanged install. The rest of this README covers the modular mcp-devices edition.


Install in 3 steps (modular)

Requires Node.js 20 or newer.

# 1. base server
npm i -g mcp-devices

# 2. add a platform (example: Android)
npm i -g @mcp-devices/plugin-android
mcp-devices install android

# 3. point your MCP client at it
#    { "mcpServers": { "mobile": { "command": "mcp-devices" } } }
# Grok Build:
#    grok plugin marketplace add AlexGladkov/claude-in-mobile
#    grok plugin install mcp-devices --trust

Restart your MCP client. Done — ask Claude "take a screenshot of my Android device" and it works.

Check prerequisites any time: mcp-devices doctor.

Native shell CLI

The npm command mcp-devices is the Node.js MCP server. For direct shell automation, install the native Rust CLI and use its unambiguous command name:

brew install AlexGladkov/tap/mcp-devices
mcp-devices-cli --help
mcp-devices-cli devices

The separate name prevents a global npm install from shadowing the native CLI on PATH.

Pick your platform

Each platform is a separate package. Install the one(s) you need — full guide in each doc:

Platform

Install

Needs

Guide

Android

npm i -g @mcp-devices/plugin-android

adb

android »

iOS

npm i -g @mcp-devices/plugin-ios

xcrun (macOS/Xcode)

ios »

Web

npm i -g @mcp-devices/plugin-web

Chrome

web »

Desktop

npm i -g @mcp-devices/plugin-desktop

Java/JDK

desktop »

Aurora

npm i -g @mcp-devices/plugin-aurora

flutter-aurora

aurora »

HarmonyOS Next

npm i -g @mcp-devices/plugin-harmony

hdc (DevEco Studio)

harmony »

All

npm i -g @mcp-devices/plugin-all

—

—

After installing a package, enable it: mcp-devices install <name> (or all), then restart.

What it can do

  • Drive apps — screenshots, taps/swipes/typing, app launch, UI tree, shell, logs, permissions, files.

  • Debug live apps — breakpoints, stepping, inspect variables, evaluate expressions (Android JDWP + iOS LLDB). See debug ».

  • Test — visual regression, accessibility audit, performance, sensor/network simulation.

These come as ~20 built-in tool modules plus the on-demand debug plugin — full tool catalog ».

Switching from all-in-one to modular?

Happy with the bundled claude-in-mobile? Do nothing — it stays maintained and installs exactly as before. This section is only if you want to move to the slim modular edition.

  • The Node MCP commands claude-in-mobile and mcp-devices keep working; the native shell interface is available as mcp-devices-cli.

  • The only difference is that platforms aren't bundled — install the one(s) you actually use:

npm i -g mcp-devices
npm i -g @mcp-devices/plugin-android   # (or plugin-all for everything)
mcp-devices install android

Tools, actions, and MCP client config are identical to the bundled edition.

Docs

Notes

  • The modular base loads no platforms by default — enable them with mcp-devices install <name>. The claude-in-mobile edition enables all.

  • Enable the separately installed debug plugin with mcp-devices plugin enable debug; MCP_DEVICES_TOOL_PLUGINS=debug remains available as a per-run override.

  • Prefer everything in one package? Use the all-in-one claude-in-mobile edition (npm i -g claude-in-mobile) — still maintained, install unchanged.

Available Tools

14 tools
appC

App lifecycle: launch, stop, install, list

Inputs: action (required), path, delayMs, package, +3 more.

deviceA

Device management + module loading. list/set/set_target/get_target: devices. enable_module/disable_module/list_modules: load browser/desktop/store tools on demand.

Inputs: action (required), module, target, category, +2 more.

flowA

Flow orchestration: batch (multi-command), run (multi-step automation with loops/conditionals), parallel (same action on multiple devices). Use turbo:true for rich feedback (experimental).

Inputs: action (required), args, steps, turbo, +5 more.

inputC

Input actions. tap/double_tap/long_press: coords or text/id/label/index. swipe: direction or coords. text: type text. key: press key.

Inputs: action (required), x, y, x1, +15 more.

repl_expectB

Block until a prompt regex matches, the session idles, the child exits, or the timeout fires.

Inputs: id (required), regex, idleMs, timeoutMs.

repl_keyA

Send a control key (enter/ctrl-c/ctrl-d/tab/arrows) to a session.

Inputs: id (required), key (required).

repl_killA

Terminate a REPL session (SIGTERM, then SIGKILL).

Inputs: id (required).

repl_listB

List active REPL sessions and their statuses.

Inputs: no named parameters.

repl_sendB

Write text to a REPL session. Appends a newline by default.

Inputs: id (required), text (required), newline.

repl_snapshotB

Read the current emulated terminal screen for a session. Output is redacted for common secret patterns unless disabled at plugin construction time.

Inputs: id (required), tail.

repl_spawnA

Start an interactive REPL or CLI process under a PTY. Returns the session id. cmd is exec'd directly (argv split, no shell): env-var prefixes, redirections (2>&1), pipes and globs are NOT interpreted — pass env via the env param, or set shell:true to run cmd through /bin/sh -c.

Inputs: id (required), cmd (required), cwd, env, +4 more.

screenB

Screen capture and annotation. capture: screenshot with compression/diff. annotate: screenshot with element bounding boxes.

Inputs: action (required), diff, preset, quality, +8 more.

systemC

System operations, clipboard, permissions, files. shell: run command. logs: device logs. clipboard_*: Android clipboard. permission_*: app permissions. file_*: Aurora file transfer.

Inputs: action (required), ms, tag, url, +10 more.

uiB

UI inspection and interaction. tree: accessibility tree. find: search elements. find_tap: fuzzy tap (Android). tap_text: tap by text (Desktop). analyze: screen analysis. wait/assert_visible/assert_gone: element checks.

Inputs: action (required), pid, text, fresh, +16 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (input vs. screen vs. ui vs. app lifecycle). However, 'input' and 'ui' both handle taps/texts, which could cause confusion; 'repl_*' tools are clearly separate but 'repl_spawn' vs 'repl_send' might overlap slightly in purpose.

    Naming Consistency4/5

    Tools mostly follow single-word or verb_noun patterns, with 'repl_*' prefix consistently used. However, mixed styles like 'tap_text' vs 'find_tap' and 'repl_spawn' vs 'spawn' deviation from a uniform convention, though the naming is generally predictable.

    Tool Count4/5

    14 tools is within the ideal 3-15 range, slightly on the higher end but each covers a distinct functionality area. The count feels appropriate for a mobile automation server, though some categories could be consolidated.

    Completeness4/5

    The tool surface covers core mobile automation needs: input, UI inspection, app lifecycle, device management, screen capture, and flow orchestration. Missing are some advanced operations like gesture composition or multi-touch, and the 'system' category is broad but shallow. Overall, no critical gaps for basic workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessUsually handled

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Android devices through UI manipulation, screen capture, touch gestures, text input, and app management via ADB. Provides comprehensive mobile automation capabilities including element detection, navigation, and application control for Android device testing and interaction.
      9
      61 PyPI
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.
      13 npm
      8
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
      6
      5 npm
      MIT