mobridge-mcp 0.10.2 → 0.10.3

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/integrity.json CHANGED
@@ -1,4 +1,4 @@
1
1
  {
2
- "buildId": "2cfde9a-20261103171312",
3
- "bundleSha256": "fb33de05ca4e23a9c4b25a9661f08b928f050b3c06ab21221f3f7f2abf9ec1d7"
2
+ "buildId": "ae04e85-20261104131248",
3
+ "bundleSha256": "ef0bd0a881391e9b586923feab712d2857c34b4e6df2a136b15fc9ca699098db"
4
4
  }
package/loader.cjs CHANGED
@@ -14,7 +14,7 @@ const os = require("node:os");
14
14
  const path = require("node:path");
15
15
  const crypto = require("node:crypto");
16
16
 
17
- const BUILD_ID = "2cfde9a-20261103171312"; // pack-npx stamps the real build id
17
+ const BUILD_ID = "ae04e85-20261104131248"; // pack-npx stamps the real build id
18
18
  const ROOT = __dirname; // package root (loader.cjs sits here)
19
19
  const DIST = path.join(ROOT, "dist");
20
20
  const BUNDLE = path.join(DIST, "main.obf.cjs");
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mobridge-mcp",
3
- "version": "0.10.2",
3
+ "version": "0.10.3",
4
4
  "description": "MoBridge MCP — a stdio MCP server exposing on-device Android UIs as fast semantic read / observe / find / act / verify tools plus screenshots. Ships an installer that wires it into Claude Code, Claude Desktop, Cursor and Codex.",
5
5
  "keywords": [
6
6
  "mcp",
@@ -5,15 +5,15 @@
5
5
  },
6
6
  "mobridge-companion-setup": {
7
7
  "version": "1.1.0",
8
- "digest": "12a409e4d043a1c3"
8
+ "digest": "b2193b406c0d058a"
9
9
  },
10
10
  "mobridge-core": {
11
11
  "version": "1.0.1",
12
12
  "digest": "9a2823d9aa9e6eaf"
13
13
  },
14
14
  "mobridge-debugging": {
15
- "version": "1.0.1",
16
- "digest": "e7cdfa202cf19add"
15
+ "version": "1.0.2",
16
+ "digest": "8f754a895e91ac5a"
17
17
  },
18
18
  "mobridge-devices": {
19
19
  "version": "1.0.1",
@@ -24,6 +24,7 @@ The owner switches go back to their defaults (install and permissions on, protec
24
24
  | `COMPANION_VERSION_MISMATCH` persists | `mobridge connect` once more; if it repeats `mobridge doctor` |
25
25
  | `COMPANION_INSTALL_FAILED` | Free storage, check minimum SDK, retry |
26
26
  | The daemon runs an old build (`DAEMON_BUILD_MISMATCH`) | `mobridge daemon restart` |
27
+ | Android lists the service under "Crashed services" (often right after an upgrade), `ACCESSIBILITY_CRASHED` | `mobridge connect` switches the MoBridge service off and on once and retries; if it repeats, toggle MoBridge Runtime in Settings > Accessibility |
27
28
  | A stale forward points at another phone (`DEVICE_BINDING_MISMATCH`) | `mobridge connect -d ANDROID:<serial>`, then `mobridge doctor` |
28
29
  | Wrong APK picked up | Set `MSM_COMPANION_APK` to the APK inside this package, or reinstall with `npx -y mobridge-mcp@latest install` |
29
30
 
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: mobridge-debugging
3
3
  description: Use when a MoBridge call fails, times out, is ambiguous, flaky or stuck, or returns an error.code
4
- version: 1.0.1
4
+ version: 1.0.2
5
5
  ---
6
6
 
7
7
  # MoBridge debugging
@@ -22,7 +22,8 @@ Every code below comes with `cause`, `recoverable`, `agentAction` and, when a pe
22
22
  | `ACCESSIBILITY_DISABLED` | The Accessibility service is off. | yes | Run `mobridge connect`; it enables the service over adb and reads it back. |
23
23
  | `ACCESSIBILITY_ENABLE_BLOCKED` | The phone does not let adb enable the Accessibility service. | no | Show the user `userAction`, then run `mobridge connect --wait-user 120` to resume the moment it is on. **User:** Settings > Accessibility > MoBridge Runtime > On. Android 13+: first Settings > Apps > MoBridge Runtime > ⋮ > Allow restricted settings. Xiaomi: Developer options > USB debugging (Security settings). |
24
24
  | `WAITING_FOR_USER_ACCESSIBILITY` | Waiting for the person to turn Accessibility on; the wait window ended. | no | Ask the user to finish the step, then run `mobridge connect` again (it resumes; nothing is reinstalled). **User:** Settings > Accessibility > MoBridge Runtime > On. |
25
- | `ACCESSIBILITY_PREEMPTED` | The service is enabled but not bound; another owner took the session. | yes | Wait a few seconds and run `mobridge connect`. |
25
+ | `ACCESSIBILITY_PREEMPTED` | The service is enabled but Android shows it unbound (the OEM killed it, or an install left it half-bound). | yes | Run `mobridge connect`: it switches the service off and on once and retries. If it repeats, check `dumpsys accessibility` for another service or UiAutomation. |
26
+ | `ACCESSIBILITY_CRASHED` | Android lists the MoBridge accessibility service under Crashed services; it is not running even if it looks enabled. | yes | Run `mobridge connect` (it toggles the service off and on). If it repeats, toggle MoBridge Runtime in Settings > Accessibility. |
26
27
  | `EXTERNAL_INSTRUMENTATION_ACTIVE` | Another tool holds UiAutomation (uiautomator, a test runner, another agent). | no | Fail fast: ask the user to stop the other tool, then `mobridge connect`. **User:** Stop the other automation tool on this phone. |
27
28
  | `TRANSPORT_DEGRADED` | The link to the phone dropped. | yes | Retry the read; for a mutation check `mobridge operation status <operationId>` first. Prefer USB over wireless adb. |
28
29
  | `WS_CONNECTION_LOST` | The WebSocket to the companion closed. | yes | Reads retry by themselves; a mutation reports RESULT_UNKNOWN, so look its operation up, never resend it. |