@maind-dev/mcp-bridge 0.136.0 → 0.137.0

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 CHANGED
@@ -49,6 +49,19 @@ official LTS build from nodejs.org (SHA-256 checked, into
49
49
  they keep working in clients whose `PATH` has no Node.js. Running it again
50
50
  updates the bridge; `rm -rf ~/.local/share/maind` removes what it installed.
51
51
 
52
+ On Windows, in PowerShell (Windows PowerShell 5.1 or PowerShell 7):
53
+
54
+ ```powershell
55
+ irm https://maind.dev/install.ps1 | iex
56
+ ```
57
+
58
+ does the same: it looks for Node.js 20+ on the `PATH`, in Program Files,
59
+ nvm-windows, Volta, fnm, Scoop and mise, or downloads the official LTS zip
60
+ from nodejs.org (SHA-256 checked, into `%LOCALAPPDATA%\maind\node`, no
61
+ administrator rights), installs the bridge into `%LOCALAPPDATA%\maind\bridge`
62
+ and runs `install`. Arguments go through a script block:
63
+ `& ([scriptblock]::Create((irm https://maind.dev/install.ps1))) --client cursor`.
64
+
52
65
  Add this to your MCP client's config (`.mcp.json` or equivalent):
53
66
 
54
67
  ```json
@@ -781,7 +794,8 @@ respects the proxy env vars on Node 22+.
781
794
  is missing from the `PATH` of the shell that ran the command. That also
782
795
  happens with Node.js installed: nvm and Homebrew put it on the `PATH` in the
783
796
  shell profile, and an agent's shell does not always read that. Run
784
- `curl -fsSL https://maind.dev/install.sh | sh` (macOS, Linux) — see
797
+ `curl -fsSL https://maind.dev/install.sh | sh` (macOS, Linux) or
798
+ `irm https://maind.dev/install.ps1 | iex` (Windows PowerShell) — see
785
799
  [Install / configure](#install--configure).
786
800
 
787
801
  **`npx` can't reach `registry.npmjs.org`.** Install the bridge globally