mcp-mobile

MCP Mobile Server exposes a suite of AI-powered tools tailored for mobile development, enabling intelligent automation, device orchestration, and cross-platform build and test workflows. The server integrates with Claude Desktop and other MCP clients to execute high-level commands like flutter_dev_session, flutter_run, flutter_release_build, and a broad set of utilities under Core Tools, Device Management, Development, and Advanced Workflows. Use the Claude/Desktop integration example to register the server as an MCP endpoint, then invoke workflows via natural language prompts or direct tool calls. The included tools cover environment setup, device discovery, hot-reload sessions, automated testing, and multi-platform release builds, all designed to streamline Flutter, Android, and iOS workflows from a single interface.

Prerequisites:

• Node.js 18.0+ and npm or yarn installed on your machine
• Access to a terminal/command prompt
• Optional: Claude Desktop or any MCP client for CLI/JSON-RPC interactions

Install globally (recommended):

npm install -g @cristianoaredes/mcp-mobile-server

Or run directly with npx without a global install:

npx @cristianoaredes/mcp-mobile-server

Verify installation by listing or health checks (examples depend on the specific CLI available in your environment):

mcp-mobile-server health_check

Configure your MCP client (e.g., Claude Desktop) to point to the server endpoint, typically via an MCP JSON-RPC configuration referencing the npm package name as shown in the Quick Start example.

Tips and considerations:

• The MCP Mobile Server ships with a large suite of tools; start with health_check and flutter_setup_environment to bootstrap a Flutter workflow.
• When integrating with Claude Desktop, you can register the server under a name like mobile-dev with command npx and args ["@cristianoaredes/mcp-mobile-server"] to enable seamless functionality.
• Ensure your development environment has Flutter, Android SDK, or Xcode installed to unlock the full toolchain capabilities.
• If you encounter permission or path issues, run the CLI with appropriate permissions or adjust PATH so that npx can execute the package binaries.
• You can expand or customize the environment by adding env variables in the mcp_config section if required by your deployment environment.