Mobile Next MCP
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 |
|---|---|
| mobile_list_available_devicesA | List all available devices. This includes both physical devices and simulators. If there is more than one device returned, you need to let the user select one of them. |
| mobile_list_appsA | List all the installed apps on the device |
| mobile_launch_appA | Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device. |
| mobile_terminate_appB | Stop and terminate an app on mobile device |
| mobile_install_appB | Install an app on mobile device |
| mobile_uninstall_appB | Uninstall an app from mobile device |
| mobile_get_screen_sizeA | Get the screen size of the mobile device in pixels |
| mobile_click_on_screen_at_coordinatesA | Click on the screen at given x,y coordinates. If clicking on an element, use the list_elements_on_screen tool to find the coordinates. |
| mobile_double_tap_on_screenA | Double-tap on the screen at given x,y coordinates. |
| mobile_long_press_on_screen_at_coordinatesA | Long press on the screen at given x,y coordinates. If long pressing on an element, use the list_elements_on_screen tool to find the coordinates. |
| mobile_list_elements_on_screenA | List elements on screen and their coordinates, with display text or accessibility label. Do not cache this result. |
| mobile_press_buttonC | Press a button on device |
| mobile_open_urlA | Open a URL in browser on device |
| mobile_swipe_on_screenC | Swipe on the screen |
| mobile_type_keysA | Type text into the focused element |
| mobile_save_screenshotB | Save a screenshot of the mobile device to a file |
| mobile_take_screenshotA | Take a screenshot of the mobile device. Use this to understand what's on screen, if you need to press an element that is available through view hierarchy then you must list elements on screen instead. Do not cache this result. |
| mobile_set_orientationA | Change the screen orientation of the device |
| mobile_get_orientationA | Get the current screen orientation of the device |
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 19 tools
Every tool has a clearly distinct purpose with no ambiguity; actions like click, double-tap, long press, swipe, and type are well-differentiated, and resource targets (e.g., apps, screen, orientation) are specific. The descriptions provide clear guidance on when to use each tool, preventing misselection.
All tool names follow a consistent 'mobile_verb_noun' pattern with snake_case throughout, such as mobile_click_on_screen_at_coordinates and mobile_list_apps. This predictability makes the set easy to navigate and understand at a glance.
With 19 tools, the count is well-scoped for mobile device automation, covering essential actions like interaction, app management, and device control. Each tool earns its place by addressing a specific need without redundancy, fitting the domain's complexity appropriately.
The toolset provides complete coverage for mobile automation, including CRUD-like operations for apps (install, launch, terminate, uninstall), screen interaction (click, swipe, type), device management (orientation, screen size), and diagnostics (screenshot, element listing). No obvious gaps exist for core workflows.