Krova Node is the JS/TS package monorepo for Krova Cloud, centrally managing various JavaScript/TypeScript tools used to operate Krova Cloud. According to official information, the repository contains the following packages: SDK, CLI, MCP server, webhook validator, and n8n node. Its main purpose is to provide and manage Krova Cloud Cubes—Firecracker-based microVMs with root access, while also supporting custom domains, TCP port mapping, and snapshots.
Structurally, this is a pnpm-workspace monorepo. The CLI and MCP reference the SDK via the workspace:* protocol, so all packages stay in sync, and cross-package changes can be completed with a single PR.
In terms of usage, users can call it in code via the SDK or operate it from the command line via the CLI; the MCP server can be used for clients that support the MCP protocol; the webhook validator is used to verify webhook requests; and the n8n node is used to integrate Krova Cloud functionality into the n8n automation platform.
The release process is automated, with no need to manually modify version numbers. Every push to the main branch runs scripts/release.mjs: for each package that has changed since the last release tag, its latest version on npm is incremented by a patch, published (with provenance), and a git tag and GitHub release for <name>@<version> are recorded. Unchanged packages are skipped. If a higher version is explicitly set in the package.json within the package, it is published at that version. Publishing uses npm trusted publishing (OIDC), and the release workflow has id-token: write permission and runs pnpm publish --provenance, so no NPM_TOKEN or any long-lived npm token is needed.
Applicable scenarios include: developers who need to manage Krova Cloud microVMs programmatically or from the command line, users who need to integrate Krova Cloud into n8n workflows, server-side applications that need to implement webhook verification, withand AI tool users who want to connect to Krova Cloud via the MCP protocol.
In terms of limitations, the current information does not provide specific system requirements, installation commands, detailed usage steps, a complete list of supported operating systems (only badges suggest possible multi-platform support), pricing information, or performance metrics.
