@firfi/huly-mcp 0.49.4 → 0.49.6
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 +16 -0
- package/dist/index.cjs +212330 -195518
- package/package.json +20 -11
package/README.md
CHANGED
|
@@ -21,6 +21,22 @@ Huly MCP and Huly CLI are maintained together in this monorepo and derive from t
|
|
|
21
21
|
|
|
22
22
|
## Installation
|
|
23
23
|
|
|
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.
|
|
39
|
+
|
|
24
40
|
The standard configuration works with most MCP clients:
|
|
25
41
|
|
|
26
42
|
```json
|