Android Mobile Mcp

Created By
erichung906010 months ago
Android Mobile MCP is a server implementation that bridges the Model Context Protocol with Android device automation capabilities. It provides a comprehensive set of tools for interacting with Android devices, including UI element detection, touch interactions, text input, app management, and screenshot capture.
Overview

what is Android Mobile MCP?

Android Mobile MCP is a server implementation that bridges the Model Context Protocol with Android device automation capabilities, providing tools for interacting with Android devices.

how to use Android Mobile MCP?

To use Android Mobile MCP, install it using the command uvx android-mobile-mcp, ensure USB debugging is enabled on your Android device, and connect it via USB or network.

key features of Android Mobile MCP?

  • UI element detection and interaction
  • Touch interactions and text input
  • App management capabilities
  • Screenshot capture functionality

use cases of Android Mobile MCP?

  1. Automating UI testing for Android applications
  2. Managing and launching apps on Android devices
  3. Capturing screenshots for documentation or testing purposes

FAQ from Android Mobile MCP?

  • What is required to use Android Mobile MCP?

You need to have USB debugging enabled, ADB installed, and your device connected.

  • Can I use Android Mobile MCP wirelessly?

Yes, if your device is accessible over the network.

  • Is there any support for other platforms?

Currently, Android Mobile MCP is focused on Android devices only.

Server Config

{
  "mcpServers": {
    "android-mobile-mcp": {
      "command": "uvx",
      "args": [
        "android-mobile-mcp"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
8 months ago
Author Name
erichung9060
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago