Krova runs on your own machine — the client starts it, so there is no endpoint to ping. 816 installs a week from npm. Last commit 3 Nov 2026.
Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, args, { stdio: "ignore", detached: true, shell: process.platform === "win32" });
"SSH public key written to the Cube login user's authorized_keys at boot — ~/.ssh/authorized_keys for the ubuntu or debian user, /root/.ssh/authorized_keys on Cubes created before the default-user change. Use get_cube_ssh to learn which user a given Cube logs in as. M…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -e 'KROVA_API_KEY=<KROVA_API_KEY>' -- npx -y @krovacloud/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp"
],
"env": {
"KROVA_API_KEY": "<KROVA_API_KEY>"
}
}
}
}[mcp_servers.mcp]
command = "npx"
args = ["-y", "@krovacloud/mcp"]
env = { KROVA_API_KEY = "<KROVA_API_KEY>" }{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp"
],
"env": {
"KROVA_API_KEY": "<KROVA_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp"
],
"env": {
"KROVA_API_KEY": "<KROVA_API_KEY>"
}
}
}
}Put your own value in place of
<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).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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).
Alternatives to Krova
same job, measured the same wayMCP server for Superserve sandboxes: create, exec, and manage Firecracker microVMs
Manage files, folders, and team collaboration with access controls
Read project context and manage tasks in MCPBinder, with access you control.
Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change.
Manage nonprofit board agendas, minutes, decisions, and action items with human approval.
Publish AI reports as managed native links with versions, access control, revocation, and audit.
Manage Nginx Proxy Manager hosts, certificates, streams and access lists with dry-run previews.
Disposable Firecracker microVM sandboxes for agents: run code, snapshot, fork. Needs Linux with KVM.
Krova — questions
Answers built from our own checks of this server.