@firfi/huly-mcp 0.49.5 → 0.49.7
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 +27 -1
- package/dist/index.cjs +211277 -190242
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -21,7 +21,21 @@ Huly MCP and Huly CLI are maintained together in this monorepo and derive from t
|
|
|
21
21
|
|
|
22
22
|
## Installation
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
### Node.js requirement
|
|
25
|
+
|
|
26
|
+
Huly MCP requires **Node.js 22.19.0 or later**. MCP clients do not provide a Node.js runtime: `node`, `npx`,
|
|
27
|
+
and the `#!/usr/bin/env node` package executable resolve Node.js from the environment in which the MCP client
|
|
28
|
+
runs. Check that environment before installation:
|
|
29
|
+
|
|
30
|
+
```bash
|
|
31
|
+
node --version
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
If an MCP client starts Huly MCP with an older runtime, Huly MCP initializes a diagnostic-only MCP surface instead
|
|
35
|
+
of loading the incompatible application. Its server instructions and `get_huly_startup_diagnostic` tool report the
|
|
36
|
+
detected executable and required version, and the same `unsupported Node.js runtime` diagnostic is written to
|
|
37
|
+
stderr. Upgrade Node.js or configure the MCP server command to use the absolute path of a compatible Node.js
|
|
38
|
+
executable, then restart the MCP server. Huly operations remain unavailable until the runtime is upgraded.
|
|
25
39
|
|
|
26
40
|
The standard configuration works with most MCP clients:
|
|
27
41
|
|
|
@@ -195,6 +209,18 @@ The `@latest` tag asks the package runner for the newest version. Some MCP clien
|
|
|
195
209
|
| **Pi** | Run `/mcp reconnect huly`, then `/reload` if the registered direct-tool surface changed |
|
|
196
210
|
| **npx (manual)** | `npx -y @firfi/huly-mcp@latest` — the `-y` flag auto-confirms install prompts |
|
|
197
211
|
|
|
212
|
+
## Maintainer Production Release
|
|
213
|
+
|
|
214
|
+
Publish from a clean, current `master` checkout with the preferred certified Node.js runtime:
|
|
215
|
+
|
|
216
|
+
```bash
|
|
217
|
+
mise exec node@24.15.0 -- pnpm local-release
|
|
218
|
+
```
|
|
219
|
+
|
|
220
|
+
Use this exact command even when a newer Node.js version is active on the host. The release build accepts only the
|
|
221
|
+
exact Node.js versions certified by CI; this is intentionally narrower than the package's runtime requirement. See
|
|
222
|
+
the [production release guide](docs/NPM_PRODUCTION_RELEASE.md) for preflight checks, rerun behavior, and verification.
|
|
223
|
+
|
|
198
224
|
## HTTP Transport
|
|
199
225
|
|
|
200
226
|
By default, the server uses stdio transport. For HTTP transport:
|