native-devtools-mcp 0.4.0 → 0.4.2

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 (2) hide show
  1. package/README.md +2 -13
  2. package/package.json +10 -5
package/README.md CHANGED
@@ -84,11 +84,6 @@ cargo build --release
84
84
  # Binary: ./target/release/native-devtools-mcp
85
85
  ```
86
86
 
87
- To include Android device support, enable the `android` feature flag:
88
-
89
- ```bash
90
- cargo build --release --features android
91
- ```
92
87
  </details>
93
88
 
94
89
  ## ⚙️ Configuration
@@ -186,7 +181,7 @@ Optional inputs like `mask_id`, `search_region`, `scales`, and `rotations` can i
186
181
 
187
182
  ## 📱 Android Support
188
183
 
189
- Android support is available as an optional feature flag. It lets the MCP server communicate with Android devices over ADB (USB or Wi-Fi), providing screenshots, input simulation, UI element search, and app management.
184
+ Android support is built-in. The MCP server communicates with Android devices over ADB (USB or Wi-Fi), providing screenshots, input simulation, UI element search, and app management.
190
185
 
191
186
  ### Prerequisites
192
187
 
@@ -194,12 +189,6 @@ Android support is available as an optional feature flag. It lets the MCP server
194
189
  2. **USB debugging enabled** on the Android device (Settings > Developer options > USB debugging)
195
190
  3. **ADB server running** — starts automatically when you run `adb devices`
196
191
 
197
- ### Building with Android support
198
-
199
- ```bash
200
- cargo build --release --features android
201
- ```
202
-
203
192
  ### Android tools
204
193
 
205
194
  All Android tools are prefixed with `android_` and appear dynamically after connecting to a device:
@@ -250,7 +239,7 @@ android_click(x=..., y=...) → tap it
250
239
  Smoke tests verify all Android tools against a real connected device. They are `#[ignore]`d by default and must be run explicitly:
251
240
 
252
241
  ```bash
253
- cargo test --features android --test android_smoke_tests -- --ignored --test-threads=1
242
+ cargo test --test android_smoke_tests -- --ignored --test-threads=1
254
243
  ```
255
244
 
256
245
  Tests must run sequentially (`--test-threads=1`) since they share a single physical device. The device must be unlocked and awake.
package/package.json CHANGED
@@ -1,7 +1,8 @@
1
1
  {
2
2
  "name": "native-devtools-mcp",
3
- "version": "0.4.0",
4
- "description": "MCP server for native desktop app testing — screenshot, OCR, click, type, find_text, template matching. macOS & Windows.",
3
+ "version": "0.4.2",
4
+ "mcpName": "io.github.sh3ll3x3c/native-devtools",
5
+ "description": "MCP server for native app testing — screenshot, OCR, click, type, find_text, template matching. macOS, Windows & Android.",
5
6
  "license": "MIT",
6
7
  "repository": {
7
8
  "type": "git",
@@ -39,7 +40,11 @@
39
40
  "testing",
40
41
  "automation",
41
42
  "macos",
42
- "windows"
43
+ "windows",
44
+ "android",
45
+ "adb",
46
+ "mobile-testing",
47
+ "mobile-automation"
43
48
  ],
44
49
  "bin": {
45
50
  "native-devtools-mcp": "bin/cli.js"
@@ -48,8 +53,8 @@
48
53
  "bin"
49
54
  ],
50
55
  "optionalDependencies": {
51
- "@sh3ll3x3c/native-devtools-mcp-darwin-arm64": "0.4.0",
52
- "@sh3ll3x3c/native-devtools-mcp-win32-x64": "0.4.0"
56
+ "@sh3ll3x3c/native-devtools-mcp-darwin-arm64": "0.4.2",
57
+ "@sh3ll3x3c/native-devtools-mcp-win32-x64": "0.4.2"
53
58
  },
54
59
  "engines": {
55
60
  "node": ">=18"