Android Mobile MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOBILEMCP_AUTH | Yes | Shared secret used as bearer token for authenticating requests to the MCP server. | |
| ADB_SERVER_SOCKET | No | Optional socket address for the ADB server, e.g. tcp:127.0.0.1:5037, when running in Docker with host networking. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mobile_list_available_devicesA | List all available devices. This includes both physical mobile devices and mobile simulators and emulators. It returns both Android and iOS devices. These are local devices already connected to this machine, ready to use immediately at no cost - for devices from the shared remote cloud fleet, use mobile_list_remote_devices instead. |
| mobile_login_to_cloud_providerA | Start authenticating this machine with the remote device cloud provider. This is required once before mobile_list_remote_devices or mobile_allocate_remote_device will work; if either of those fails with an authentication error, call this tool and then retry. This starts a browser-based device-code login and returns quickly with a URL and a one-time code - it does NOT wait for the login to complete. Show the URL and code to the user verbatim and ask them to open the URL and enter the code in their own browser. The login keeps running in the background after this tool returns; once the user confirms they've completed it, retry the remote devices tool that originally failed. Only call this after the user has explicitly asked to connect to, log into, or use remote/cloud devices - never call it speculatively, since it interrupts the user to act in their browser. |
| mobile_list_remote_devicesA | List the catalog of device models (make, platform, OS version) available to reserve from the remote cloud device fleet. This is different from mobile_list_available_devices, which lists real devices and simulators/emulators already connected to this local machine and ready to use immediately at no cost. Remote devices live in a shared cloud fleet: they are not usable until reserved with mobile_allocate_remote_device, and reserving one may be a limited/billed resource. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry. |
| mobile_allocate_remote_deviceA | Reserve a physical device from the remote cloud fleet for exclusive use, returning a device identifier usable with the other mobile_* tools. Unlike local devices, a remote device is a shared and billed resource borrowed for the session - only call this after the user has explicitly asked to use a remote/cloud device, never speculatively or as a fallback when a local device isn't found. Requires mobile_login_to_cloud_provider to have been called first; if this fails with an authentication error, call that tool then retry. Use mobile_list_remote_devices first to see which names and versions actually exist in the fleet before filtering by them. Release the device with mobile_release_remote_device once the whole task is finished - releasing wipes the device's state, so do not release and reallocate between steps of the same task just to be tidy. |
| mobile_release_remote_deviceA | Release a device previously reserved with mobile_allocate_remote_device back to the remote cloud fleet so it becomes available to others. Releasing is destructive to the device's state: apps installed, files pushed, and any other changes made during this session are lost, and a later mobile_allocate_remote_device call may take time and could return a different physical unit. Only release once the whole task is finished - if there is more work to do on the same device shortly, keep holding it rather than releasing and reallocating. |
| 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_appC | 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_screenB | Double-tap on the screen at given x,y coordinates. |
| mobile_long_press_on_screen_at_coordinatesB | 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_urlB | 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_orientationB | Change the screen orientation of the device |
| mobile_get_orientationB | Get the current screen orientation of the device |
| mobile_start_screen_recordingA | Start recording the screen of a mobile device. The recording runs in the background until stopped with mobile_stop_screen_recording. Returns the path where the recording will be saved. |
| mobile_stop_screen_recordingA | Stop an active screen recording on a mobile device. Returns the file path, size, and approximate duration of the recording. |
| mobile_list_crashesB | List crash reports available on the device |
| mobile_get_crashA | Get the full content of a crash report by its ID. Use mobile_list_crashes to find available crash IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaboluManohar/DevAutoFlow-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server