@buoy-gg/mcp 7.0.3 → 7.0.5
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/README.md +17 -0
- package/dist/{chunk-MGZN6MJE.mjs → chunk-KZFJFXI4.mjs} +514 -75
- package/dist/cli.js +648 -203
- package/dist/cli.mjs +8 -2
- package/dist/index.d.mts +45 -4
- package/dist/index.d.ts +45 -4
- package/dist/index.js +641 -202
- package/dist/index.mjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -18,17 +18,34 @@ One command, non-destructive:
|
|
|
18
18
|
|
|
19
19
|
The config it writes launches the server via `npx -y @buoy-gg/mcp@latest`, so every editor restart re-resolves the newest published version — you never get pinned to a stale copy. Restart your editor, open your app with Buoy running, and start with `list_devices`.
|
|
20
20
|
|
|
21
|
+
### Corporate / private npm registries
|
|
22
|
+
|
|
23
|
+
If your machine's `.npmrc` points npm at a private registry that isn't reachable (a common setup on work laptops, e.g. off-VPN), `npx @latest` would hang trying to download the package on every editor launch — so `init` probes that registry first and, when it's unreachable, automatically installs a **pinned local copy** (from public npm) and writes a `node <path>` config instead. That takes the network off the startup path entirely.
|
|
24
|
+
|
|
25
|
+
You can also force it:
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
npx -y @buoy-gg/mcp@latest init --local # always install locally, no network on startup
|
|
29
|
+
npx -y @buoy-gg/mcp@latest init --npx # always use the auto-updating npx entry
|
|
30
|
+
npx -y @buoy-gg/mcp@latest init --registry <url> # registry the local install pulls from
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
To update a local install later, just re-run `init`.
|
|
34
|
+
|
|
21
35
|
## What your agent can do
|
|
22
36
|
|
|
23
37
|
**Read the runtime**
|
|
24
38
|
|
|
25
39
|
- `get_events` — one timeline across every tool: network, state changes, renders, routes, storage writes — in token-friendly summaries
|
|
26
40
|
- `get_console` — read the app's console logs, even from a release build
|
|
41
|
+
- `get_network_requests` — HTTP requests *with their ids* (which `get_events` omits), marked 📌 pinned / 🔖 saved; `flagged:"any"` reads the requests you kept
|
|
42
|
+
- `network_action` — pin or save a request. Pinned requests survive Clear, the history cap and restarts, so it doubles as a handoff: pin the broken call and ask your agent about "the pinned request", or let it pin what it wants you to see
|
|
27
43
|
|
|
28
44
|
**Drive the UI**
|
|
29
45
|
|
|
30
46
|
- `describe_screen` — walks the live React tree into an accessibility-style element list with labels, testIDs, control values, and tap points
|
|
31
47
|
- `tap_element` — presses real JS handlers: tap a button, flip a switch, move a slider, type into a field. No screenshots, no pixel coordinates, works on physical devices. Off-screen targets are scrolled into view first.
|
|
48
|
+
- `reload_app` — restarts the JS bundle (Expo Go, dev client, or RN CLI) and waits for the app to come back, for changes Fast Refresh missed or a clean-slate startup. Ships with `@buoy-gg/core` — no extra package needed.
|
|
32
49
|
|
|
33
50
|
**Change state**
|
|
34
51
|
|