@firfi/huly-mcp 0.55.3 → 0.55.5-next.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.
Files changed (9) hide show
  1. package/README.md +4 -3
  2. package/dist/application.cjs +22977 -19962
  3. package/dist/index.cjs +1 -1
  4. package/dist/native/THIRD-PARTY-NOTICES +0 -687
  5. package/dist/native/huly-stdio-darwin-arm64 +0 -0
  6. package/dist/native/huly-stdio-darwin-x64 +0 -0
  7. package/dist/native/huly-stdio-linux-arm64 +0 -0
  8. package/dist/native/huly-stdio-linux-x64 +0 -0
  9. package/package.json +6 -27
package/README.md CHANGED
@@ -70,11 +70,12 @@ Exact native tool names still dispatch when a client calls them directly, but ma
70
70
  <details>
71
71
  <summary>Codex</summary>
72
72
 
73
- Codex must wait for Huly during its first package download. The 120-second client startup allowance includes package installation; the server's resident startup budget remains 30 seconds. Add this server to `~/.codex/config.toml`:
73
+ `npx` automatically downloads and caches Huly MCP; `pnpm dlx @firfi/huly-mcp@latest` is an alternative. Huly is optional, so Codex can start without it and a cold download may leave the first turn without Huly tools. Run `/mcp` to check the connection.
74
+
75
+ Add to `~/.codex/config.toml` (the 120-second startup allowance includes installation):
74
76
 
75
77
  ```toml
76
78
  [mcp_servers.huly]
77
- required = true
78
79
  startup_timeout_sec = 120
79
80
  command = "npx"
80
81
  args = ["-y", "@firfi/huly-mcp@latest"]
@@ -219,7 +220,7 @@ the [production release guide](docs/NPM_PRODUCTION_RELEASE.md) for preflight che
219
220
 
220
221
  ## Shared resident stdio
221
222
 
222
- The setup examples explicitly select `MCP_TRANSPORT=stdio-resident`. MCP clients still use stdio, while compatible clients under the same OS user share a Node backend through small native bridges. Linux and macOS arm64/x64 binaries are included; no Rust installation is needed. MCP initialization and the tool catalog are available while the resident starts. Codex's `required=true` setting separately makes its first model turn wait for MCP, including the initial package download; a server cannot advertise tools before its package has been installed. A temporary ordinary stdio process serves this protocol metadata through the same registry and exposure rules, without waiting for a Huly connection. Application requests remain buffered during the 30-second resident startup budget. Successful attachment retires the temporary process; startup failure keeps it as ordinary stdio and dispatches the buffered application input once. A failed active resident never reconnects or replays application requests.
223
+ The setup examples explicitly select `MCP_TRANSPORT=stdio-resident`. MCP clients still use stdio, while compatible clients under the same OS user share a Node backend through small native bridges. Linux and macOS arm64/x64 binaries are included; no Rust installation is needed. Application requests remain buffered during the 30-second resident startup budget. Startup failure launches ordinary stdio and dispatches the buffered application input once. A failed active resident never reconnects or replays application requests.
223
224
 
224
225
  Omitting `MCP_TRANSPORT` still selects ordinary `stdio`, preserving existing installations. Set `MCP_TRANSPORT=stdio` explicitly to keep a separate backend per client. Restart the MCP client after changing the setting.
225
226