@mobilenext/mobile-mcp 0.0.6 → 0.0.8

package/README.md

@@ -1,11 +1,13 @@
 ## Mobile Next - MCP server for Mobile Automation
 
-This is a [Model Context Protocol (MCP) server](https://github.com/modelcontextprotocol) that provides mobile automation capabilities powered by [Appium](https://github.com/appium). 
+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.
 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. 
 
+
+
 <p align="center">
     <a href="https://github.com/mobile-next/">
-        <img alt="mobile-mcp" src="https://github.com/mobile-next/mobile-next-assets/blob/main/mobile-mcp-banner.png?raw=true" width="600">
+        <img alt="mobile-mcp" src="https://raw.githubusercontent.com/mobile-next/mobile-next-assets/refs/heads/main/mobile-mcp-banner.png" width="600">
     </a>
 </p>
 
@@ -37,8 +39,8 @@ How we help to scale mobile automation:
 ## Mobile MCP Architecture
 
 <p align="center">
-    <a href="/images/mobile-mcp-arch.png">
-        <img alt="mobile-mcp" src="https://github.com/mobile-next/mobile-next-assets/blob/main/mobile-mcp-arch.png?raw=true" width="600">
+    <a href="https://raw.githubusercontent.com/mobile-next/mobile-next-assets/refs/heads/main/mobile-mcp-arch.png">
+        <img alt="mobile-mcp" src="https://raw.githubusercontent.com/mobile-next/mobile-next-assets/refs/heads/main/mobile-mcp-arch.png" width="600">
     </a>
 </p>
 
@@ -52,7 +54,7 @@ How we help to scale mobile automation:
     "mobile-next": {
       "command": "npx",
       "args": [
-        "@mobile-next/appium-mcp@latest"
+        "@mobilenext/mobile-mcp@latest"
       ]
     }
   }
@@ -70,23 +72,23 @@ What you will need to connect MCP with your agent and mobile devices:
 
 ### Simulators, Emulators, and Physical Devices
 
-When launched, Appium MCP can connect to:
+When launched, Mobile MCP can connect to:
 	•	iOS Simulators on macOS/Linux
 	•	Android Emulators on Linux/Windows/macOS
 	•	Physical iOS or Android devices (requires proper platform tools and drivers)
 
-Make sure you have your mobile platform SDKs (Xcode, Android SDK) installed and configured properly before running Mobile Next Appium MCP.
+Make sure you have your mobile platform SDKs (Xcode, Android SDK) installed and configured properly before running Mobile Next Mobile MCP.
 
 
 ### Running in "headless" mode on Simulators/Emulators
 
-When you do not have an actual phone connected, you can run Mobile Next Appium MCP with an emulator or simulator in the background.
+When you do not have an actual phone connected, you can run Mobile Next Mobile MCP with an emulator or simulator in the background.
 
 For example, on Android:
 	1.	Start an emulator (avdmanager / emulator command).
-	2.	Run Appium MCP with the desired flags
+	2.	Run Mobile MCP with the desired flags
 
-On iOS, you'll need Xcode and to run the Simulator before using Appium MCP with that simulator instance.
+On iOS, you'll need Xcode and to run the Simulator before using Mobile MCP with that simulator instance.
 `xcrun simctl list`
 `xcrun simctl boot "iPhone 16"`
 
@@ -166,7 +168,7 @@ These tools use accessibility-based element references on iOS or Android. By rel
   - `time` (number): Time to wait in seconds (capped at 10 seconds)
 
 ## mobile_close_session
-- **Description:** Closes the current Appium session
+- **Description:** Closes the current device session
 - **Parameters:** None
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mobilenext/mobile-mcp",
-  "version": "0.0.6",
+  "version": "0.0.8",
   "description": "Mobile MCP",
   "repository": {
     "type": "git",
@@ -14,6 +14,7 @@
     "build": "tsc",
     "lint": "eslint .",
     "watch": "tsc --watch",
+    "start": "node lib/index.js",
     "clean": "rm -rf lib"
   },
   "exports": {