mobile-dev

The Mobile Development MCP server provides a collection of tools to manage and interact with mobile devices and simulators (Android and iOS) from a unified MCP interface. It supports device lifecycle operations, app installation and launching, file transfers, UI automation (taps, swipes, text input), and comprehensive logging and diagnostics. Use the included tools to enumerate devices, install or launch apps, capture screenshots, push and pull files, and automate common UI interactions on both Android and iOS environments. The server is designed to work with ADB for Android, Xcode CLI tools for iOS simulators, and optional IDB tooling for advanced iOS UI automation. When running, you can query and invoke the listed tools to perform tasks such as listing devices, capturing logs, taking screenshots, or automating UI actions on target devices.

Prerequisites:

• ADB (Android Debug Bridge) installed and in your PATH
• Xcode Command Line Tools installed for iOS simulator management (xcrun simctl)
• Optional: Facebook IDB tool for iOS UI automation (see IDB installation guide)
• .NET SDK (e.g., .NET 9)

Installation steps:

1. Clone the repository git clone https://github.com/jsuarezruiz/mobile-dev-mcp-server.git

2. Navigate to the project directory cd mobile-dev-mcp-server

3. Build the project dotnet build

4. Run the MCP server (example, using the path from the README) { "mcp-server-mobiledev": { "type": "stdio", "command": "dotnet", "args": [ "run", "--project", "/Users/jsuarezruiz/GitHub/mobile-dev-mcp-server/src/MobileDevMcpServer.csproj" ] } }

5. (Optional) Test with the MCP Inspector using the npm-based inspector tool npm i -g @modelcontextprotocol/inspector npx @modelcontextprotocol/inspector dotnet run

6. If you need to customize environment variables, adjust the mcp_config in your client setup as needed.

Tips and notes:

• Ensure ADB is accessible from your PATH for Android device management.
• For iOS UI automation, IDB is required and should be installed per the IDB docs.
• The MCP server exposes a rich set of tools (see Tools section in the README) including Android and iOS device listing, installation, app launching, logs, and UI interactions.
• If you encounter permissions issues on macOS, ensure you have the necessary developer permissions for simctl and device access.
• The mcp_config uses a .NET-based run approach; you can adapt the command or environment as needed for your environment. Common environment variables include ASPNETCORE_ENVIRONMENT and MCP_LOG_LEVEL for easier debugging.
• When integrating with clients, you can run the server in development mode and switch to production configurations by adjusting the environment and logging levels.