← Back to directory
I

io.github.qwenlm/mobile-mcp

Community
Mobile automation and testing MCP server for iOS and Android, forked from mobile-mcp with relative coordinate support.
GitHub source repository ↗
★ 26.7k Stars Category · Dev Tools Very popular
34FMRS · D
Reliability
6/20
Security and permissions
7/20
Maintenance
12/20
Documentation
4/20
Setup experience
5/20

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.

Read the FMRS scoring method →

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.

Tools

The tool list has not been reviewed yet.

Setup

  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.
claude_desktop_config.json
{"mcpServers":{"mobile-mcp":{"command":"npx","args":["-y","@qwen-code/mobile-mcp"]}}}

Fit and risk

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

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

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

Supported clients

Supported clients have not been confirmed yet.