@maind-dev/mcp-bridge 0.132.0 → 0.132.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.
- package/README.md +25 -0
- package/build/index.js +340 -340
- package/build/meta.json +1 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -29,8 +29,26 @@ pairings.
|
|
|
29
29
|
|
|
30
30
|
## Install / configure
|
|
31
31
|
|
|
32
|
+
**Requires Node.js 20 or later.** `npx` is part of Node.js; without it on the
|
|
33
|
+
`PATH` the commands below end in `command not found`.
|
|
34
|
+
|
|
32
35
|
You normally don't install anything — `npx` fetches the bridge on first run.
|
|
33
36
|
|
|
37
|
+
**No Node.js, or the agent's shell does not find it?** On macOS and Linux
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
curl -fsSL https://maind.dev/install.sh | sh
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
finds a Node.js 20+ on this machine — on the `PATH`, in the usual version
|
|
44
|
+
managers (nvm, Volta, fnm, asdf, mise, nodenv), in Homebrew — or downloads the
|
|
45
|
+
official LTS build from nodejs.org (SHA-256 checked, into
|
|
46
|
+
`~/.local/share/maind/node`, no sudo). It then installs the bridge into
|
|
47
|
+
`~/.local/share/maind/bridge` and runs `install` with the arguments you pass
|
|
48
|
+
(`… | sh -s -- --client cursor`). The client configs name absolute paths, so
|
|
49
|
+
they keep working in clients whose `PATH` has no Node.js. Running it again
|
|
50
|
+
updates the bridge; `rm -rf ~/.local/share/maind` removes what it installed.
|
|
51
|
+
|
|
34
52
|
Add this to your MCP client's config (`.mcp.json` or equivalent):
|
|
35
53
|
|
|
36
54
|
```json
|
|
@@ -730,6 +748,13 @@ the page, click Approve.
|
|
|
730
748
|
launching your MCP client. The bridge uses Node's built-in `fetch`, which
|
|
731
749
|
respects the proxy env vars on Node 22+.
|
|
732
750
|
|
|
751
|
+
**`npx: command not found`, or `npm`/`node` not found.** Node.js 20 or later
|
|
752
|
+
is missing from the `PATH` of the shell that ran the command. That also
|
|
753
|
+
happens with Node.js installed: nvm and Homebrew put it on the `PATH` in the
|
|
754
|
+
shell profile, and an agent's shell does not always read that. Run
|
|
755
|
+
`curl -fsSL https://maind.dev/install.sh | sh` (macOS, Linux) — see
|
|
756
|
+
[Install / configure](#install--configure).
|
|
757
|
+
|
|
733
758
|
**`npx` can't reach `registry.npmjs.org`.** Install the bridge globally
|
|
734
759
|
(`npm install -g @maind-dev/mcp-bridge`) and point your `.mcp.json` at
|
|
735
760
|
`"command": "maind-mcp-bridge"` instead of `npx`.
|