mobridge-mcp 0.12.4 → 0.13.1

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.
Files changed (10) hide show
  1. package/AI-USAGE.md +2 -0
  2. package/dist/main.obf.cjs +1 -1
  3. package/integrity.json +2 -2
  4. package/loader.cjs +1 -1
  5. package/package.json +1 -1
  6. package/resources/android/app-developer-release.apk +0 -0
  7. package/skills/VERSIONS.json +6 -6
  8. package/skills/mobridge-adb/SKILL.md +3 -1
  9. package/skills/mobridge-companion-setup/SKILL.md +7 -1
  10. package/skills/mobridge-devices/SKILL.md +26 -1
package/AI-USAGE.md CHANGED
@@ -32,6 +32,8 @@ One connect call handles installation: it installs the companion APK if missing,
32
32
  enables Accessibility over adb, creates the adb forward and then performs the handshake. You do not run adb or install the APK by hand.
33
33
  After an install/update, connect waits for the companion to become ready (a few seconds at most), so no immediate second call is needed.
34
34
 
35
+ No cable: connect with transport "companion-lan" (the user scans the QR in the MoBridge app; UI only, plus shell and files when a Shizuku shell is ready) or "adb-wireless" (the user scans it in Wireless debugging; full adb). Both return PAUSED with a QR: put it in your reply (the PNG is attached; if images are not shown, paste the ASCII block that follows in a fenced code block), say it expires in about 2 minutes, then call connect again with the pairingSessionId (expired: call connect again for a fresh QR). The connect result keeps `connections` (links) apart from `shell` (backend, uid); UNSUPPORTED_ON_TIER means this link has no shell or adb. After one QR pairing with the "allow reconnect" switch on, the phone redials the computer by its enrolled key with no QR (keep the "keep connected" switch on; a connect result with `reconnect` and no PAUSED means it worked); list or revoke enrolled phones with `mobridge reconnect list|forget <id|all>`. Root is never carried over: the owner re-enables the Root lease on the phone after each reconnect.
36
+
35
37
  1. mobridge devices (or mobile.device.connect) to get the deviceId; with several devices always pass deviceId.
36
38
  2. mobile.device.connect / mobridge connect -d ANDROID:<serial>. Read ready, blockers, warnings, provision.companionInstalled
37
39
  (ALREADY | INSTALLED | UPDATED) and health.accessibility.