MCP Mobile Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flutter_doctorB | Run Flutter doctor to check development environment setup |
| flutter_versionB | Get Flutter SDK version information |
| flutter_list_devicesB | List connected devices and emulators available for Flutter development |
| android_list_devicesA | List connected Android devices and emulators (supports ADB fallback to native-run) |
| native_run_list_devicesC | List connected devices using native-run (Android & iOS support) |
| native_run_install_appC | Install app on device using native-run (works for Android APK & iOS app) |
| ios_list_simulatorsB | List available iOS simulators |
| android_list_emulatorsB | List available Android emulators |
| android_create_avdC | Create a new Android Virtual Device (AVD) |
| android_start_emulatorC | Start an Android emulator |
| android_stop_emulatorC | Stop a running Android emulator |
| ios_shutdown_simulatorC | Shutdown an iOS simulator |
| flutter_launch_emulatorC | Launch a Flutter emulator |
| flutter_runC | Start a Flutter development session (hot reload enabled) |
| flutter_buildC | Build Flutter app for specific target platform |
| flutter_testC | Run Flutter tests with optional coverage |
| flutter_cleanB | Clean Flutter build cache and generated files |
| flutter_pub_getC | Install Flutter project dependencies (pub get) |
| android_install_apkC | Install an APK file to an Android device or emulator |
| android_logcatC | Capture Android logcat output from device or emulator |
| android_screenshotC | Capture screenshot from Android device or emulator |
| ios_boot_simulatorC | Boot an iOS simulator |
| ios_take_screenshotC | Take a screenshot of an iOS simulator |
| flutter_dev_sessionB | Complete Flutter dev setup: check env, list devices, select best device, run with hot reload |
| flutter_test_suiteC | Run complete test suite: unit tests, widget tests, integration tests with coverage report |
| flutter_release_buildC | Build release versions for all platforms: APK, AAB, IPA with signing |
| mobile_device_managerC | Smart device management: list all, recommend best, auto-start if needed |
| flutter_fix_common_issuesC | Auto-fix common issues: clean, pub get, pod install, gradle sync, invalidate caches |
| flutter_setup_environmentC | Complete Flutter SDK installation and environment setup with automatic path configuration |
| android_sdk_setupC | Setup Android SDK and configure environment for Android development |
| health_checkB | Check server health, tool availability and environment status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools have distinct purposes, but there is some overlap between Android and Flutter device listing tools (e.g., android_list_devices vs. flutter_list_devices vs. native_run_list_devices) that could cause confusion. The descriptions help differentiate, but the boundaries are not perfectly clear.
Tool names follow a consistent snake_case pattern with clear prefixes (android_, flutter_, ios_, etc.) and verb_noun structure throughout. This makes the set predictable and easy to navigate, with no deviations in naming conventions.
With 31 tools, the count is borderline high for a mobile development server, feeling heavy and potentially overwhelming. While the tools cover Android, Flutter, and iOS comprehensively, the number could be streamlined without losing functionality.
The tool surface provides complete coverage for mobile development workflows, including setup, device management, building, testing, and debugging across Android, Flutter, and iOS. There are no obvious gaps, and agents can handle typical tasks without dead ends.