Android Mobile Mcp

Created By
tree8 months ago
Android Mobile MCP bridges the Model Context Protocol with Android device automation, enabling AI agents to interact with Android devices through UI manipulation, app management, and screen capture.
Overview

what is Android Mobile MCP?

Android Mobile MCP bridges the Model Context Protocol with Android device automation, enabling AI agents to interact with Android devices through UI manipulation, app management, and screen capture.

how to use Android Mobile MCP?

To use Android Mobile MCP, connect your Android device via USB or network, enable USB debugging, and install ADB (Android Debug Bridge). Configure the MCP settings and utilize the provided tools for various interactions.

key features of Android Mobile MCP?

  • UI manipulation through screen analysis and interaction tools.
  • App management capabilities including listing and launching applications.
  • Screen capture for visual analysis.
  • Touch interactions like clicking and swiping.
  • Text input into focused fields.

use cases of Android Mobile MCP?

  1. Automating app testing on Android devices.
  2. Creating AI-driven interactions with mobile applications.
  3. Capturing and analyzing screen states for debugging purposes.

FAQ from Android Mobile MCP?

  • What devices are compatible with Android Mobile MCP?

Any Android device that supports USB debugging and ADB can be used.

  • Is there a specific Android version required?

The tool is designed to work with most modern Android versions that support ADB.

  • Can I use this tool for remote device management?

Yes, as long as the device is connected to the same network or via USB.

Server Config

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago