How do I install Krova Node?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Krova Node need an API key?

The publisher lists these environment variables: KROVA_API_KEY, KROVA_SPACE_ID, KROVA_BASE_URL.

What transport does Krova Node use?

Krova Node runs locally over stdio.

Krova Node

by cloud.krova

Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y @krovacloud/[email protected]

Credentials from the publisher

KROVA_API_KEY — A Krova Cloud API key, created under Settings → API keys. Scoped to one Space and inherits the permissions of the membership that created it.
KROVA_SPACE_ID — Optional. A Space id the Cube tools default to, so a client does not have to name a Space on every call.
KROVA_BASE_URL — Optional. Overrides the API base URL. Only needed against a non-production environment.

Provider

Claude Code

KROVA_API_KEY=<secret> KROVA_SPACE_ID=<value> KROVA_BASE_URL=<value> claude mcp add cloud.krova-mcp -- npx -y @krovacloud/[email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "cloud.krova-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@krovacloud/[email protected]"
      ],
      "env": {
        "KROVA_API_KEY": "<secret>",
        "KROVA_SPACE_ID": "<value>",
        "KROVA_BASE_URL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Krova Node?: Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Krova Node need an API key?: The publisher lists these environment variables: KROVA_API_KEY, KROVA_SPACE_ID, KROVA_BASE_URL.
What transport does Krova Node use?: Krova Node runs locally over stdio.
When was Krova Node last checked?: Last checked 2026-10-16. Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.

krova-node

The single home for the Krova Cloud JavaScript / TypeScript packages — SDK, CLI, MCP server, webhook verifier, and the n8n node. A pnpm-workspace monorepo: the CLI/MCP consume the SDK via workspace:*, so everything stays in sync and a cross-package change is one PR.

Package	npm	What it is
`packages/sdk`	`@krovacloud/sdk`	Typed TypeScript SDK for the Krova Cloud API
`packages/cli`	`@krovacloud/cli`	The `krova` CLI (pure Node — built on the SDK)
`packages/mcp`	`@krovacloud/mcp`	MCP server for Claude/Cursor/etc.
`packages/webhook`	`@krovacloud/webhook`	Outbound-webhook signature verification
`packages/n8n-node`	`n8n-nodes-krova`	n8n community node

Develop

pnpm install
pnpm -r build      # topological — the SDK builds before its consumers
pnpm -r test
pnpm -r typecheck

Releasing (automatic, no manual version bumps)

Every push to main runs scripts/release.mjs: for each package that changed since its last release tag, it patch-increments the latest version on npm, publishes it (with provenance), and records a <name>@<version> git tag + GitHub release. Unchanged packages are skipped. An explicit higher version in a package's package.json is honored as-is.

Publishing uses npm trusted publishing (OIDC) — the release workflow has id-token: write and runs pnpm publish --provenance, so no NPM_TOKEN (or any long-lived npm token) is required. See "How releases work" in CONTRIBUTING.md.