@mobilenext/mobile-mcp 0.0.6 → 0.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,8 +1,10 @@
|
|
|
1
1
|
## Mobile Next - MCP server for Mobile Automation
|
|
2
2
|
|
|
3
|
-
This is a [Model Context Protocol (MCP) server](https://github.com/modelcontextprotocol) that
|
|
3
|
+
This is a [Model Context Protocol (MCP) server](https://github.com/modelcontextprotocol) that enables scalable mobile automation through a platform-agnostic interface, eliminating the need for distinct iOS or Android knowledge.
|
|
4
4
|
This server allows Agents and LLMs to interact with native iOS/Android applications and devices through structured accessibility snapshots or coordinate-based taps based on screenshots.
|
|
5
5
|
|
|
6
|
+
|
|
7
|
+
|
|
6
8
|
<p align="center">
|
|
7
9
|
<a href="https://github.com/mobile-next/">
|
|
8
10
|
<img alt="mobile-mcp" src="https://github.com/mobile-next/mobile-next-assets/blob/main/mobile-mcp-banner.png?raw=true" width="600">
|
|
@@ -52,7 +54,7 @@ How we help to scale mobile automation:
|
|
|
52
54
|
"mobile-next": {
|
|
53
55
|
"command": "npx",
|
|
54
56
|
"args": [
|
|
55
|
-
"@mobile-
|
|
57
|
+
"@mobilenext/mobile-mcp@latest"
|
|
56
58
|
]
|
|
57
59
|
}
|
|
58
60
|
}
|
|
@@ -70,23 +72,23 @@ What you will need to connect MCP with your agent and mobile devices:
|
|
|
70
72
|
|
|
71
73
|
### Simulators, Emulators, and Physical Devices
|
|
72
74
|
|
|
73
|
-
When launched,
|
|
75
|
+
When launched, Mobile MCP can connect to:
|
|
74
76
|
• iOS Simulators on macOS/Linux
|
|
75
77
|
• Android Emulators on Linux/Windows/macOS
|
|
76
78
|
• Physical iOS or Android devices (requires proper platform tools and drivers)
|
|
77
79
|
|
|
78
|
-
Make sure you have your mobile platform SDKs (Xcode, Android SDK) installed and configured properly before running Mobile Next
|
|
80
|
+
Make sure you have your mobile platform SDKs (Xcode, Android SDK) installed and configured properly before running Mobile Next Mobile MCP.
|
|
79
81
|
|
|
80
82
|
|
|
81
83
|
### Running in "headless" mode on Simulators/Emulators
|
|
82
84
|
|
|
83
|
-
When you do not have an actual phone connected, you can run Mobile Next
|
|
85
|
+
When you do not have an actual phone connected, you can run Mobile Next Mobile MCP with an emulator or simulator in the background.
|
|
84
86
|
|
|
85
87
|
For example, on Android:
|
|
86
88
|
1. Start an emulator (avdmanager / emulator command).
|
|
87
|
-
2. Run
|
|
89
|
+
2. Run Mobile MCP with the desired flags
|
|
88
90
|
|
|
89
|
-
On iOS, you'll need Xcode and to run the Simulator before using
|
|
91
|
+
On iOS, you'll need Xcode and to run the Simulator before using Mobile MCP with that simulator instance.
|
|
90
92
|
`xcrun simctl list`
|
|
91
93
|
`xcrun simctl boot "iPhone 16"`
|
|
92
94
|
|
|
@@ -166,7 +168,7 @@ These tools use accessibility-based element references on iOS or Android. By rel
|
|
|
166
168
|
- `time` (number): Time to wait in seconds (capped at 10 seconds)
|
|
167
169
|
|
|
168
170
|
## mobile_close_session
|
|
169
|
-
- **Description:** Closes the current
|
|
171
|
+
- **Description:** Closes the current device session
|
|
170
172
|
- **Parameters:** None
|
|
171
173
|
|
|
172
174
|
|