Krova MCP server
{
"mcpServers": {
"krova": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@latest"
]
}
}
}{
"mcpServers": {
"krova": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@latest"
]
}
}
}{
"mcpServers": {
"krova": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@latest"
]
}
}
}{
"servers": {
"krova": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@latest"
]
}
}
}{
"mcpServers": {
"krova": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @krovacloud/mcpversion 0.3.14
What it does
An MCP server that exposes the Krova Cloud API for provisioning and managing Firecracker microVMs. It is part of a monorepo containing a TypeScript SDK, CLI, and other Krova Cloud tooling, allowing Claude, Cursor, and other AI assistants to interact with Krova Cloud resources.
- Provision new Krova Cloud Cubes (Firecracker microVMs) with root access through Claude or Cursor.
- Query and manage existing Krova Cloud microVMs programmatically via the MCP server.
- Integrate Krova Cloud infrastructure operations into AI-assisted workflows.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.