cloud.krova/mcp
Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@krovacloud/mcpclaude mcp add cloud-krova-mcp -e 'KROVA_API_KEY=<your krova_api_key>' -e 'KROVA_SPACE_ID=<KROVA_SPACE_ID>' -e 'KROVA_BASE_URL=<KROVA_BASE_URL>' -- npx -y @krovacloud/mcp@0.3.19
{
"mcpServers": {
"cloud-krova-mcp": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@0.3.19"
],
"env": {
"KROVA_API_KEY": "<your krova_api_key>",
"KROVA_SPACE_ID": "<KROVA_SPACE_ID>",
"KROVA_BASE_URL": "<KROVA_BASE_URL>"
}
}
}
}
Environment variables
KROVA_API_KEYrequired secret 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_IDOptional. A Space id the Cube tools default to, so a client does not have to name a Space on every call.KROVA_BASE_URLOptional. Overrides the API base URL. Only needed against a non-production environment.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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.
Frequently asked questions
What is cloud.krova/mcp?
Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.
How do I install cloud.krova/mcp?
It runs on your machine. In Claude Code: claude mcp add cloud-krova-mcp -e 'KROVA_API_KEY=<your krova_api_key>' -e 'KROVA_SPACE_ID=<KROVA_SPACE_ID>' -e 'KROVA_BASE_URL=<KROVA_BASE_URL>' -- npx -y @krovacloud/mcp@0.3.19. For other clients, paste the JSON configuration from this page into their MCP settings.
Does cloud.krova/mcp need an API key?
Yes. It expects KROVA_API_KEY, which you set in its configuration.
Is cloud.krova/mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains cloud.krova/mcp?
It is published by krovacloud. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.