M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

Mobile MCP

Community
Mobile automation and testing MCP server for iOS and Android, forked from mobile-mcp with relative coordinate support.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #394 of 438
Stars
★ 29.0k Very popular
Transport
stdio (local process)
Runtime
Node.js
Credentials
No credential needed
License
Apache-2.0
Last commit
34FMRS · D

This entry is an MCP server manifest in the qwen-code repository for mobile automation and testing, published as an npm package over stdio transport, and forked from the mobile-mcp project with added relative coordinate support. The source material provides no explicit tool list or client compatibility evidence, so those fields are left empty; the assessment is limited to facts confirmable from the manifest and repository description.

Strongest · Maintenance 12/20 Weakest · Documentation 4/20

Reliability
6/20
Security and permissions
7/20
Maintenance
12/20
Documentation
4/20
Setup experience
5/20
Why each score
Reliability 6/20
The manifest only declares an npm package (@qwen-code/mobile-mcp) with stdio transport, and the version field is still the unresolved template placeholder {{VERSION}}, indicating this manifest has not passed through an actual release/validation process. There is no evidence in the provided material of any CI workflow, unit/integration tests, tool list, or init/handshake behavior specific to the mobile-mcp subpackage; the parent repository's general activity cannot substitute for reproducibility evidence of this specific server. Per the static calibration rule, without verifiable execution evidence reliability cannot exceed 12, and given the unresolved version placeholder and complete absence of a tool list or error-handling description, a low score is warranted.
Security and permissions 7/20
Mobile device automation (iOS/Android control, UI testing) typically involves ADB/simulator access, app install/uninstall, and screen manipulation with real-world side effects, yet the material contains no permission model, least-privilege description, confirmation mechanism for dangerous operations, or data-boundary disclosure. The server is described as a 'fork (with relative coordinate support)' with no stated maintainer identity or relationship to the upstream project, and no disclosure of network or credential usage. No red-line evidence (malware, credential theft, etc.) was found, but given the complete absence of permission/confirmation information for a tool with potentially high-impact device operations, only a mid-low score is justified.
Maintenance 12/20
The parent qwen-code repository has high star count (26,728), a large number of open issues (855), and a clear Apache-2.0 license, indicating the overall project is actively maintained with reasonably clear governance. However, mobile-mcp is a subpackage nested within this monorepo (packages/mobile-mcp), and no subpackage-specific release history, versioning cadence, or security-response channel evidence is present in the material — its maintenance activity can only partially borrow credibility from the parent repo and cannot be independently verified.
Documentation 4/20
The provided README is the generic top-level introduction to the qwen-code project and makes no mention anywhere of mobile-mcp or mobile automation capabilities; it contains no installation steps, tool parameters, authentication method, limitations, or troubleshooting content for this specific server. The manifest itself is extremely sparse, containing only the package identifier and transport type, with no usage examples. There is almost no correspondence between the documentation and this server's actual capabilities, warranting a very low score.
Setup experience 5/20
Beyond the npm package identifier and stdio transport type, the manifest provides no client configuration example (e.g., args, env, client config snippet), and the version field remains an unresolved placeholder, suggesting this configuration may not yet be finalized or validated for actual use. There is no indication that a mainstream MCP client (e.g., Claude Desktop) could connect using this configuration as-is. Per the static calibration rule, setup cannot exceed 15 without verifiable execution evidence, and given the near-total absence of installation information in the actual material, a very low score is warranted.

Static review · not runListed 2026-08-06

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Teams using qwen-code or another MCP-capable coding agent for mobile app development
  • Developers who want AI-assisted iOS/Android UI automation and testing
  • Automation scenarios that benefit from relative rather than absolute screen coordinates for cross-device consistency

Not for

  • General programming tasks unrelated to mobile development or testing
  • Scenarios requiring browser automation, database access, or cloud storage integration
  • Users without access to an iOS/Android device, simulator, or emulator environment

Required permissions

  • Access to and control over local or connected iOS/Android simulators, emulators, or physical devices
  • Ability to install, launch, and operate applications on the target device
  • Screen capture and touch/coordinate input on the device

Risks and side effects

  • As a community fork, this server may lag behind upstream mobile-mcp security fixes and updates
  • Granting an AI agent automated control over mobile devices risks unintended actions, data loss, or corrupted app state
  • The source material does not list specific tools, so the actual scope of exposed operations and permission boundaries is opaque without inspecting the published package directly
  • Running a third-party npm package without independent security audit carries supply-chain risk

Setup

Before you start

Runtime：Node.js

  1. Ensure Node.js 22 or later is installed (the requirement stated for the parent qwen-code project).
  2. Install or run the @qwen-code/mobile-mcp package via npm/npx (registry: https://registry.npmjs.org).
  3. In an MCP client that supports stdio transport, add this server to mcpServers with command set to npx and args set to ["-y", "@qwen-code/mobile-mcp"].
  4. Make sure a local iOS simulator/device or Android emulator/device and the relevant tooling (Xcode command line tools, adb) are set up so the server can connect to and drive a mobile device.
  5. Restart or reload the client to pick up the new MCP server.
MCP config · JSON 
{"mcpServers":{"mobile-mcp":{"command":"npx","args":["-y","@qwen-code/mobile-mcp"]}}}

Works in clients that read an "mcpServers" key. For clients such as VS Code that use a different key, the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@qwen-code/mobile-mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add mobile-mcp -- npx -y @qwen-code/mobile-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Add the mobile-mcp server to your client config (npx -y @qwen-code/mobile-mcp), restart the client, and check that mobile-mcp tools appear in the tool list. Asking "list connected mobile devices" and getting a device response confirms the connection.

Troubleshooting

  1. Verify Node.js version meets the >=22.0.0 requirement
  2. Confirm @qwen-code/mobile-mcp installed correctly from the npm registry and that the {{VERSION}} placeholder resolved to a concrete version
  3. Check that an iOS/Android simulator, emulator, or physical device is properly connected and that adb or Xcode tooling is available
  4. Verify the MCP client's stdio transport configuration correctly points to this package's executable entry point

Things to try

Once connected, you can ask your AI assistant things like:

  • List the connected Android devices and show their status.
  • Take a screenshot of the current iOS simulator screen.
  • Install ./app-debug.apk on this Android device and launch the app.
  • Tap the login button on the app's login screen.

Use cases

Driving iOS/Android simulators, emulators, or real devices from an AI agent to perform UI interaction testing
Having a coding agent write, run, and verify mobile automation test scripts as part of local development or CI
Using relative-coordinate targeting for more reliable UI element interaction across different device resolutions

Overview

io.github.qwenlm/mobile-mcp is an MCP server manifest located at packages/mobile-mcp in the QwenLM/qwen-code repository, intended for iOS and Android mobile development, automation, and testing. Its description explicitly states it is a fork of the mobile-mcp project with added relative coordinate support. The server is published as the npm package @qwen-code/mobile-mcp and communicates over stdio transport. The provided source material does not enumerate a specific list of tools, so the exposed capabilities cannot be confirmed. The broader qwen-code project is an open-source, terminal-based AI coding agent supporting multiple model providers (OpenAI, Anthropic, Gemini, Qwen) and MCP integration, but the README describes the main CLI product rather than the mobile-mcp subpackage specifically.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 80953e053b40 Data synced 2026-11-04 Read the FMRS scoring method