Current versions
The current published version of each hlix package, and how to install it. Every version on this page is rendered from the release ledger, so it always matches what the registry serves.
@hlix/cli
Section titled “@hlix/cli”The hlix command: import a project, keep it in sync, and inspect projects and tasks from a terminal.
Install
npm install --global @hlix/clihlix --versionnpx @hlix/cli --helpIn CI, and anywhere the toolchain must not change underneath you, pin the version instead of floating to latest:
npm install --global @hlix/cli@0.2.0Start at Install the CLI, then Authenticate. The full command surface is in the CLI reference.
@hlix/sdk
Section titled “@hlix/sdk”The first-party TypeScript client: authentication, retries, typed errors, uploads, and SSE streaming against the same contract the CLI uses.
Install
npm install @hlix/sdkPin the version in CI so a build never picks up a client you have not tested against:
npm install @hlix/sdk@0.2.0See the TypeScript SDK for client creation, the error classes, and the retry policy. To generate a client in another language, use the OpenAPI contract directly.
@hlix/mcp
Section titled “@hlix/mcp”The official MCP server: it exposes workspace-scoped projects, tasks, cycles, comments, and review evidence to Cursor, Claude Code, Codex, and Windsurf.
Configure your client
Your MCP client launches the server itself — there is nothing to install by hand. The version is pinned so a client restart cannot silently upgrade a server holding your workspace credentials.
Save as .cursor/mcp.json in the project.
{ "mcpServers": { "hlix": { "command": "npx", "args": [ "-y", "@hlix/mcp@0.2.0" ] } }}Save as .mcp.json in the project and approve the server when prompted.
{ "mcpServers": { "hlix": { "command": "npx", "args": [ "-y", "@hlix/mcp@0.2.0" ] } }}Add to a trusted project’s .codex/config.toml or your user config.
[mcp_servers.hlix]command = "npx"args = ["-y", "@hlix/mcp@0.2.0"]default_tools_approval_mode = "writes"Add the entry to ~/.codeium/windsurf/mcp_config.json.
{ "mcpServers": { "hlix": { "command": "npx", "args": [ "-y", "@hlix/mcp@0.2.0" ] } }}Connect a client
- Authenticate once with the CLI.
Terminal window hlix auth login --workspace <workspace-id>The server reuses the owner-only credential written by the CLI. Never paste an API key into an MCP config or command argument.
- Bind the repository by importing it.
Terminal window cd /path/to/projecthlix import .hlix initselects the API and workspace but does not create or bind a cloud project. A successful import writes the project ID used for strict project scoping. - Use the version-pinned configuration above.
Restart the client or begin a new agent session, then inspect its MCP server list. A user-level global configuration can omit a local binding and operate across the selected workspace.
- Run a read-only check.
Ask the agent to list Hlix projects or read one task. In a bound repository, the server exposes only that project and rejects cross-project IDs.
See the official MCP server for the tool list, the write gate, and per-client notes.
Check what you have
Section titled “Check what you have”hlix --versionnpm view @hlix/cli versionExpected result: two version numbers. When they differ, the installed CLI is older than the registry’s current release — upgrade with the install command above, or pin deliberately.
If a version looks wrong
Section titled “If a version looks wrong”hlix --versiondisagrees withnpm view. You have an older global install. Re-run the install command, then open a new shell soPATHresolves the new binary.npm error E404on a version you see here. Check for a typo in the package name;@hlix/cli,@hlix/sdk, and@hlix/mcpare the only three.- An MCP client keeps starting an old server. The configuration pins a version. Update the pin in the client config and restart the client — the server does not self-upgrade, deliberately.
- A generated API client is missing an endpoint. It is missing from the published contract, so no client can reach it. See what the contract does not cover.