mobile-debug-mcp 0.34.0 → 0.36.0

package/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing
+
+Read the [development process](docs/specs/process.md) before planning, editing,
+or reviewing a change. Documentation and maintenance use its lightweight path;
+new capabilities and material contract changes require intent and specification
+approval. Automated contributors also start with [AGENTS.md](AGENTS.md).
+
+## Local development
+
+Use Node.js 22 or newer and npm. Platform tooling is needed only for the mobile
+operations you exercise; see [requirements and setup](README.md#requirements).
+
+```sh
+npm ci
+npm run build
+npm start
+```
+
+The TypeScript entrypoint is [src/server.ts](src/server.ts); registration and
+dispatch live in [src/server-core.ts](src/server-core.ts) and [src/server/](src/server/).
+The optional Java debugger bridge lives in
+[src/debugger/java/](src/debugger/java/). It is shipped as source and compiled
+on demand by the debugger; the TypeScript build does not compile Java.
+
+Platform operations are grouped under `src/manage/`, `src/interact/`,
+`src/observe/`, `src/debugger/`, and `src/system/`, with shared helpers in `src/utils/`.
+
+## Validation
+
+```sh
+npm run verify
+npm run test:device
+```
+
+`verify` runs lint, the TypeScript build, automated unit tests, and plugin
+consistency checks. Run applicable device checks for native or runtime changes;
+record which devices and behaviours actually ran. See the [process verification
+requirements](docs/specs/process.md#5-verify-and-report) for reporting failures,
+blocked checks, and unrun coverage. Documentation-only work needs diff, relative
+link/path, command, and consistency checks; builds and device tests are unnecessary.
+
+Load the [test-authoring skill](.agents/skills/test-authoring/SKILL.md) before
+changing tests, and the [MCP builder skill](.agents/skills/mcp-builder/SKILL.md)
+for installation or native toolchain work. Automated unit tests belong in
+`test/unit/`, automated device tests in `test/device/automated/`, and manual
+helpers in `test/device/manual/`.
+
+## Code structure
+
+Follow the [code structure and quality checks](docs/code-structure.md) for module
+ownership, enforced limits, and review of legacy exceptions. `npm run lint`
+includes ESLint, structural/type limits and ArchUnitTS dependency checks; CI runs
+the same checks. To diagnose a failure, run `npm run check:quality` or
+`npm run check:architecture` separately. Change a rule or reviewed exception only
+with the corresponding design rationale, rather than suppressing the failure.
+
+## Documentation conventions
+
+Use the [documentation index](docs/README.md) to place new material. Keep one
+page responsible for each contract and link to it from related guides. Keep
+setup in the root README, current tool contracts in `docs/tools/`, design records
+in `docs/specs/`, and measurements in `docs/benchmarks/`.
+
+Write guides around a reader's task: explain when to use the page, show a complete
+example where useful, and link to the likely next step. Keep agent usage
+workflows in the existing plugin skill and detailed contracts in the tool
+reference. Avoid duplicating the full navigation on every page; long references
+should offer task-based links to their own sections.
+
+Use one descriptive level-one heading per document and a logical heading
+hierarchy. Use relative links for repository files. Explain prerequisites before
+commands and distinguish examples, proposals, and verified behaviour. Keep
+historical approval and verification evidence dated; avoid chat-relative wording,
+agent handoff instructions, transient checkout status, and temporary log paths.
+Do not turn an earlier design decision into a current support or release claim.
+
+When usage changes, update the relevant tool reference, README, and changelog.
+When plugin metadata or its server pin changes, run `npm run sync:agent-plugin`
+and `npm run check:agent-plugin`; see the [plugin guide](agent-plugin/README.md).

package/README.md

@@ -1,56 +1,200 @@
 # Mobile Debug Tools
 [![npm version](https://img.shields.io/npm/v/mobile-debug-mcp.svg)](https://www.npmjs.com/package/mobile-debug-mcp)
 
-A minimal, secure MCP server for AI-assisted mobile development. Build, install, interact and inspect Android/iOS apps from an MCP-compatible client.
+Build, install, control, and inspect Android and iOS apps from an MCP-compatible
+client. Mobile Debug Tools connects your client to local device toolchains and
+provides UI actions, screenshots, logs, state assertions, and optional Android
+performance capture and runtime debugging.
+
+Android, iOS, and Kotlin Multiplatform projects are supported. Flutter and React
+Native have not been tested. Platform and device limitations are described in the
+[tool reference](docs/tools/TOOLS.md).
+
+## What you can use it for
+
+Mobile Debug Tools gives a coding agent access to a running app, so development
+can include feedback from the device as well as the source code. For example:
+
+- **Build and test a feature.** After adding a settings screen, build and install
+  the app, navigate to it, and check that its controls display and behave as
+  expected. See [app management](docs/tools/manage.md) and
+  [UI interactions and assertions](docs/tools/interact.md).
+- **Check a bug fix or regression.** Reproduce a sequence such as opening a form,
+  entering text and submitting it, then verify the resulting screen or control
+  state. Repeat the journey after a code change to check the outcome.
+- **Review the UI on a device.** Capture screenshots to inspect layout and visual
+  changes, or inspect the UI hierarchy for exposed labels and control state.
+  See [observations](docs/tools/observe.md).
+- **Investigate an app failure.** Collect logs, screenshots and a debug snapshot
+  around a failing action to understand what happened. [Evidence
+  correlation](docs/tools/correlated-evidence.md) links observations to the action.
+- **Investigate mobile performance or runtime behaviour.** Capture a
+  [Perfetto or iOS simulator Instruments trace](docs/tools/system-traces.md) during a slow flow, or attach the
+  [runtime debugger](docs/tools/debugger.md) to a debuggable app to inspect
+  breakpoints, call stacks and locals on Android or an iOS simulator.
+
+## How it works
+
+Your agent client launches a local MCP server and communicates with it over
+stdio. The server translates tool calls into operations through Android's ADB
+or Apple's Xcode tools and idb, then returns device observations and action
+results to the client. It connects to emulators, simulators and supported
+physical devices through those toolchains.
+
+The agent plugin bundles the server configuration and usage skill. The same
+server can also be configured directly in an MCP client or run from a source
+checkout. See [code structure](docs/code-structure.md#module-ownership) for the
+implementation's module boundaries.
+
+## Start here
+
+Choose how to connect:
+
+1. **[Agent plugin](#agent-plugin) — Recommended.** Installs the server configuration
+   and usage skill together for supported agent clients.
+2. **[Direct MCP configuration](#mcp-configuration).** Connect the published server
+   to another MCP-compatible client.
+3. **[Manual setup](#manual-setup).** Build and run a local source checkout.
+
+Check the [requirements](#requirements) for your platform before installing.
 
-> **Support:**
-> * KMP
-> * Android
-> * iOS
-> * Flutter - not tested
-> * React native - not tested
+## Requirements
 
-Actions, screenshots, trees, and logs expose [correlated evidence](docs/tools/evidence.md)
-with explicit action references, phase timestamps, and conservative freshness.
+- Node.js >= 22
+- [Android SDK](https://developer.android.com/studio) (adb) for Android support
+- Xcode and its command-line tools on macOS for iOS support
+- [idb](https://github.com/facebook/idb) for iOS UI inspection and interaction
+- JDK 17+ for optional [Android runtime debugging](docs/tools/debugger.md); Xcode’s Swift-enabled LLDB/Python for optional iOS simulator debugging
 
-Android [system traces](docs/tools/system-traces.md) can bracket existing journeys
-and return local Perfetto artifacts with explicit correlation metadata.
+## Agent plugin
 
-Android [runtime debugging](docs/tools/debugger.md) supports explicit process attach,
-source breakpoints, bounded stacks/locals, stepping, resume and owned detach.
-JDK 17+ is optional and required only for debugger tools.
+The plugin installs the MCP server configuration and the `mobile-debug-mcp` usage
+skill together. These are GitHub/local installation routes; they do not require
+approval from a client's public curated marketplace.
 
-## Requirements
+<details>
 
-- Node.js >= 18
-- [Android SDK](https://developer.android.com/studio) (adb) for Android support
-- Xcode command-line tools for iOS support
-- [idb](https://github.com/facebook/idb) for iOS device support
+<summary>Codex</summary>
+
+In a terminal with a current Codex CLI:
+
+```bash
+codex plugin marketplace add clivejefferies/mobile-debug-tools --ref main
+codex plugin add mobile-debug-tools@mobile-debug-tools
+codex plugin list
+```
+
+Start a new chat/session and confirm the plugin is enabled and its skill and MCP
+tools are available. These commands use the repository's marketplace, named
+`mobile-debug-tools`, not a public directory listing. See the
+[official packaging instructions](https://developers.openai.com/plugins/build/plugins).
 
-## Environment Setup
+</details>
+
+<details>
+
+<summary>Claude Code</summary>
+
+Run these shell commands (not slash commands inside a chat):
+
+```bash
+claude plugin marketplace add clivejefferies/mobile-debug-tools --scope user
+claude plugin install mobile-debug-tools@mobile-debug-tools --scope user
+claude plugin list
+```
+
+Restart the session after installation. In an interactive Claude Code chat, the
+corresponding commands start with `/plugin` instead of `claude plugin`. See
+[Claude Code's installation guide](https://code.claude.com/docs/en/discover-plugins).
 
-The server discovers Android and iOS tools automatically from standard locations by default. Manual environment setup is still supported, but it should be treated as the fallback for non-standard installs, overrides, or reproducible pinned toolchains.
+</details>
 
-Use explicit paths when:
-- you have multiple SDKs installed
-- the tools live outside standard locations
-- you want deterministic setup across machines
-- automatic discovery does not find the expected binary
+<details>
 
-Leave the variables unset when:
-- the tools are already on `PATH`
-- the standard Android and Xcode locations are enough
+<summary>Cursor</summary>
 
-Common environment variables:
-- `ADB_PATH`: explicit path to `adb`
-- `ANDROID_SDK_ROOT` or `ANDROID_HOME`: Android SDK root
-- `XCRUN_PATH`: explicit path to `xcrun`
-- `MCP_IDB_PATH` or `IDB_PATH`: explicit path to `idb`
-- `GRADLE_JAVA_HOME` or `JAVA_HOME`: Java home for Gradle-backed operations
+For local installation, clone this repository and run these commands from its
+root in a macOS/Linux shell:
 
-For normal use, call `get_system_status` first. It reports the detected host, Android, and iOS toolchain state so the client can decide whether automatic discovery is sufficient or whether explicit overrides are needed.
+```bash
+git clone https://github.com/clivejefferies/mobile-debug-tools.git
+cd mobile-debug-tools
+cursor_plugin_dir="$HOME/.cursor/plugins/local/mobile-debug-tools"
+if [ -e "$cursor_plugin_dir" ]; then
+  echo "Move the existing plugin directory aside before copying the new package."
+else
+  mkdir -p "$(dirname "$cursor_plugin_dir")"
+  cp -R agent-plugin/cursor "$cursor_plugin_dir"
+fi
+```
+
+On Windows, copy the contents of `agent-plugin/cursor` into a new
+`~/.cursor/plugins/local/mobile-debug-tools` folder, including `.cursor-plugin`.
+Use this generated Cursor-native package, not the portable parent: Cursor does
+not expand `${PLUGIN_DATA}` in portable `mcp.json`. Do not symlink to the checkout.
+
+Run **Developer: Reload Window**, open **Customize**, and confirm the skill and
+MCP server are loaded. For Teams/Enterprise distribution, import this repository
+under **Dashboard → Plugins & MCPs → Team Marketplaces**; its
+[Cursor catalog](.cursor-plugin/marketplace.json) selects the native package.
+Members install from Customize. See [Cursor's plugin guide](https://cursor.com/docs/plugins).
+
+</details>
+
+<details>
+
+<summary>Antigravity</summary>
+
+Install the [Antigravity CLI](https://antigravity.google/docs/getting-started?tab=cli),
+then clone this GitHub repository and export its plugin:
+
+```bash
+git clone https://github.com/clivejefferies/mobile-debug-tools.git
+cd mobile-debug-tools
+npm run package:antigravity -- "$PWD/antigravity-dist"
+agy plugin validate --strict "$PWD/antigravity-dist"
+agy plugin install "$PWD/antigravity-dist"
+agy plugin list --json
+```
+
+No `npm install` is needed for the export script. Choose a new output directory;
+the exporter refuses to overwrite an existing one. Check the installed entry has
+one skill (`mobile-debug-mcp`) and one MCP server (`mobile-debug-mcp`), then start
+a new session and approve the specific MCP calls you intend to use.
+
+The Antigravity-only export avoids strict-validation warnings from the other
+clients' compatibility files. It uses `mcp_config.json` and the same pinned npm
+server and shared skill. GitHub/local installation does not require the
+Antigravity Marketplace interest form. See [Google's plugin guide](https://antigravity.google/docs/build-plugins).
+
+</details>
+
+Each client needs Node.js 22 or newer, `npx` on its PATH, npm registry access on
+first launch, and the platform toolchains for your device. After installation,
+ask the agent to list devices, select an explicit emulator/device, and inspect
+its screen. An installed component list alone does not prove a working device
+connection. Disable any separate manual registration of this MCP server in the
+same client to avoid duplicate tools. If a plugin command is unavailable, update
+the client; the [direct MCP configuration](#mcp-configuration) works independently.
+
+## MCP configuration
+
+For a standard installation, add this stdio server to your client's MCP settings:
+
+```json
+{
+  "mcpServers": {
+    "mobile-debug": {
+      "command": "npx",
+      "args": ["--yes", "mobile-debug-mcp"]
+    }
+  }
+}
+```
 
-## MCP Configuration
+If your client uses separate fields, choose stdio, set the command to `npx`, and
+supply `--yes` and `mobile-debug-mcp` as arguments. The examples below add optional
+path overrides; replace the placeholder paths before using them.
 
 <details>
 
@@ -63,7 +207,7 @@ Recommended when you want Android only, or when you want to make the Android too
   "mcpServers": {
     "mobile-debug": {
       "command": "npx",
-      "args": ["--yes","mobile-debug-mcp","server"],
+      "args": ["--yes", "mobile-debug-mcp"],
       "env": {
         "ADB_PATH": "/path/to/adb",
         "ANDROID_SDK_ROOT": "/path/to/android/sdk",
@@ -89,7 +233,7 @@ Recommended when you want iOS simulator or device support, or when `idb` lives i
   "mcpServers": {
     "mobile-debug": {
       "command": "npx",
-      "args": ["--yes","mobile-debug-mcp","server"],
+      "args": ["--yes", "mobile-debug-mcp"],
       "env": {
         "XCRUN_PATH": "/usr/bin/xcrun",
         "MCP_IDB_PATH": "/path/to/idb",
@@ -104,107 +248,52 @@ For iOS-only setups, `ADB_PATH` and `ANDROID_SDK_ROOT` are not required unless y
 
 </details>
 
-<details>
-
-<summary>Codex</summary>
-
-Use STDIO
-
-command: npx
-
-args: 
-* --yes
-* mobile-debug-mcp
-
-environment variables:
-* ADB_PATH: /path/to/adb
-* XCRUN_PATH: /usr/bin/xcrun
-* IDB_PATH: /path/to/idb
-* MCP_IDB_PATH: /path/to/idb
-* ANDROID_SDK_ROOT: /path/to/android/sdk
-* GRADLE_JAVA_HOME: /path/to/jdk
-* JAVA_HOME: /path/to/jdk
-
-If you are unsure whether the environment is configured correctly, run `get_system_status` first. It reports the detected host, Android, and iOS toolchain state in a structured form.
-
-</details>
-
-## Agent Plugin
-
-For clients that support Agent Plugins, the [agent-plugin](agent-plugin/README.md)
-package installs the MCP server configuration together with the existing usage
-skill. Direct npm/MCP configuration above remains supported.
+## Manual setup
 
-<details>
-
-<summary>Codex plugin</summary>
-
-Install the plugin from this repository's marketplace:
+For a local source checkout, follow the [development setup](CONTRIBUTING.md#local-development)
+to install dependencies and build the server. Then configure your MCP client to
+launch that build over stdio:
 
-```bash
-codex plugin marketplace add clivejefferies/mobile-debug-tools
-codex plugin add mobile-debug-tools@mobile-debug-tools
-```
-
-</details>
-
-<details>
-
-<summary>Claude Code plugin</summary>
-
-Install the plugin from this repository's marketplace:
-
-```bash
-claude plugin marketplace add clivejefferies/mobile-debug-tools
-claude plugin install mobile-debug-tools@mobile-debug-tools
+```json
+{
+  "mcpServers": {
+    "mobile-debug": {
+      "command": "node",
+      "args": ["/absolute/path/to/mobile-debug-mcp/dist/server.js"]
+    }
+  }
+}
 ```
 
-</details>
-
-<details>
-
-<summary>Cursor plugin</summary>
-
-The repository includes a [Cursor marketplace](.cursor-plugin/marketplace.json).
-Teams and Enterprise admins can import the repository in Dashboard → Plugins & MCPs → Team
-Marketplaces. To test it locally, copy [agent-plugin](agent-plugin/) into
-`~/.cursor/plugins/local/mobile-debug-tools`, then reload Cursor.
-
-</details>
-
-Start a new chat or session after installation so the client loads the skill
-and MCP tools. Each plugin launches the published npm package locally and needs
-Node.js 18 or newer and the platform toolchains for your device. If you also
-registered the MCP server directly, disable that registration to avoid
-duplicate tools.
+Replace the path with your checkout location. Rebuild after source changes.
 
-## Usage 
+## Environment setup
 
-Crash fixing:
-> I have a crash on the app, can you diagnose it, fix and validate using the mcp tools available
+The server discovers platform tools from standard locations and `PATH`. Leave
+path overrides unset for a standard installation. Use them for non-standard
+locations, multiple toolchains, or a pinned development environment.
 
-Feature building:
-> Add a button, hook into the repository and confirm API request successful
+| Variable | Purpose |
+| --- | --- |
+| `ADB_PATH` | Path to `adb`. |
+| `ANDROID_SDK_ROOT` or `ANDROID_HOME` | Android SDK root. |
+| `XCRUN_PATH` | Path to `xcrun`. |
+| `MCP_IDB_PATH` or `IDB_PATH` | Path to `idb`. |
+| `GRADLE_JAVA_HOME` or `JAVA_HOME` | Java home for Gradle-backed operations. |
 
-For actions that depend on a previously observed UI, use an optional
-`expectedState` from `get_ui_tree` on the same explicit device. The server checks
-a fresh snapshot immediately before input and returns `PRECONDITION_FAILED`
-with current UI evidence if the state changed. See
-[conditional actions](docs/tools/interact.md#conditional-actions) for supported
-tools, examples, and the limits of the check.
+After connecting the client, call `get_system_status` to check discovery and
+prerequisites. See [environment diagnostics](docs/tools/system.md) if a toolchain
+or device is unavailable.
 
-## Docs
+Android debugger errors include bounded, sanitized failure classifications and recovery guidance; see the [debugger guide](docs/tools/debugger.md#failure-diagnostics).
 
-Use `get_app_readiness` to observe loading, transitioning, settled, or unknown UI
-state, and `wait_for_app_ready` for a bounded wait. Existing UI waits can opt into
-`requireReady: true`. Results include evidence and uncertainty; see
-[app readiness](docs/tools/observe.md#app-readiness) for limits and examples.
+## Documentation
 
-- Tools: [Tools](docs/tools/TOOLS.md) — full input/response examples
-- Changelog: [Changelog](docs/CHANGELOG.md)
-- Agents: [AGENTS.md](AGENTS.md) — cold-start guidance for autonomous agents entering the public repo
-- Skills: [.agents/skills/README.md](.agents/skills/README.md) — portable Markdown skill packages for agents such as Copilot, Codex, Claude, or custom systems
+- [Documentation guide](docs/README.md) — find the guide for your task.
+- [Tool reference](docs/tools/TOOLS.md) — inputs, responses, examples, and shared principles.
+- [Contributing](CONTRIBUTING.md) — develop the server and run its checks.
+- [Changelog](docs/CHANGELOG.md) — release history.
 
 ## License
 
-Apache-2.0
+[Apache-2.0](LICENSE)

package/agent-plugin/.antigravity-plugin/README.md

@@ -0,0 +1,48 @@
+# Mobile Debug Tools for Antigravity
+
+Inspect and interact with Android and iOS apps using a local MCP server and the
+bundled `mobile-debug-mcp` usage skill. Capture screenshots, logs and UI trees;
+verify interactions with explicit evidence. Android additionally supports optional
+runtime debugging and bounded Perfetto system traces. iOS runtime debugging and
+system traces are not supported.
+
+## Prerequisites
+
+- Node.js 22 or newer, with `npx` on PATH and npm registry access on first launch.
+- Android SDK/platform-tools and an authorized device or running emulator for Android.
+- macOS and the applicable Xcode/idb tooling for iOS.
+- Host JDK 17+ and a debuggable Android app for optional runtime debugging.
+
+The server runs locally through `npx`; its exact version is pinned in
+`mcp_config.json`. The plugin uses the client-managed `${PLUGIN_DATA}` directory as its working directory.
+No plugin-specific account, API key, OAuth sign-in or hosted backend is required.
+
+## Install and use
+
+Install the extracted plugin directory with `agy plugin install /path/to/mobile-debug-tools`.
+Run `agy plugin list --json` and confirm one skill (`mobile-debug-mcp`) and one
+MCP server (`mobile-debug-mcp`) are discovered. Start a new session. Disable a
+separate manual registration of the same MCP server to avoid duplicate tools.
+
+Example prompts:
+
+- Check my mobile debugging environment and connected devices.
+- Inspect the current screen of my mobile app.
+- Help me reproduce and diagnose a bug in my mobile app.
+
+For a first check, select an explicit emulator/device, inspect its current screen,
+and verify a harmless interaction using fresh UI evidence. Readiness is a probe;
+a dispatched action alone does not establish an app outcome.
+
+## Access and support
+
+Tools can read device screens, logs and shallow debugger locals; they can also
+interact with apps and manage their lifecycle. These may contain private data.
+Use only devices and apps you intend to inspect. Build/install/reset operations
+have their own effects and should be requested explicitly. Trace contents and
+artifacts stay local; this plugin adds no automatic upload service.
+
+Source and setup: https://github.com/clivejefferies/mobile-debug-tools
+Tool reference: https://github.com/clivejefferies/mobile-debug-tools/blob/main/docs/tools/TOOLS.md
+Support: https://github.com/clivejefferies/mobile-debug-tools/issues
+License: Apache-2.0. Publisher attribution: mobile-debug-tools contributors.

package/agent-plugin/.antigravity-plugin/plugin.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://antigravity.google/schemas/v1/plugin.json",
+  "name": "mobile-debug-tools",
+  "version": "0.0.6",
+  "description": "Mobile app debugging tools and usage guidance for Android and iOS agents.",
+  "author": {
+    "name": "mobile-debug-tools contributors"
+  },
+  "repository": "https://github.com/clivejefferies/mobile-debug-tools",
+  "license": "Apache-2.0",
+  "displayName": "Mobile Debug Tools",
+  "logo": "assets/mobile-debug-tools.svg",
+  "suggestedPrompts": [
+    "Check my mobile debugging environment and connected devices.",
+    "Inspect the current screen of my mobile app.",
+    "Help me reproduce and diagnose a bug in my mobile app."
+  ]
+}

package/agent-plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-debug-tools",
-  "version": "0.0.3",
+  "version": "0.0.6",
   "description": "Mobile app debugging tools and usage guidance for Android and iOS agents.",
   "author": {
     "name": "mobile-debug-tools contributors"
@@ -12,7 +12,7 @@
       "command": "npx",
       "args": [
         "--yes",
-        "mobile-debug-mcp@0.34.0",
+        "mobile-debug-mcp@0.36.0",
         "server"
       ]
     }

package/agent-plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-debug-tools",
-  "version": "0.0.3",
+  "version": "0.0.6",
   "description": "Mobile app debugging tools and usage guidance for Android and iOS agents.",
   "repository": "https://github.com/clivejefferies/mobile-debug-tools",
   "license": "Apache-2.0",

package/agent-plugin/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-debug-tools",
-  "version": "0.0.3",
+  "version": "0.0.6",
   "description": "Mobile app debugging tools and usage guidance for Android and iOS agents.",
   "author": {
     "name": "mobile-debug-tools contributors"
@@ -14,7 +14,7 @@
       "command": "npx",
       "args": [
         "--yes",
-        "mobile-debug-mcp@0.34.0",
+        "mobile-debug-mcp@0.36.0",
         "server"
       ],
       "cwd": "${CURSOR_PLUGIN_ROOT}"

package/agent-plugin/.mcp.json

@@ -5,7 +5,7 @@
       "command": "npx",
       "args": [
         "--yes",
-        "mobile-debug-mcp@0.34.0",
+        "mobile-debug-mcp@0.36.0",
         "server"
       ],
       "cwd": "${PLUGIN_DATA}"