Cloud MCP

@krovacloud/mcp

MCP server for [Krova Cloud](https://krova.cloud) — let Claude, Cursor, and any MCP client provision and manage Cubes (Firecracker microVMs) in natural language.

A Model Context Protocol server that exposes Krova Cloud as a set of tools an AI agent can call. Ask Claude to "spin up a 2-vCPU Ubuntu cube in us", "list my running cubes", or "power off the idle ones", and it drives the Krova Cloud API for you.

It's a thin, fully typed bridge over the official @krovacloud/sdk: each Krova Cloud operation is an MCP tool with a validated input schema, authenticated with your API key.

Quickstart

The fastest way to try it — no install, no clone:

KROVA_API_KEY=kro_... npx -y @krovacloud/mcp

The server speaks MCP over stdio, so you normally don't run it by hand — your MCP client launches it with that command. Pick your client below.

Remote server (no install)

Krova Cloud also hosts this server at https://krova.cloud/mcp over Streamable HTTP. It exposes the same tools as this package, so there is nothing to install.

ChatGPT and Claude.ai

Add a custom connector with the URL https://krova.cloud/mcp. Sign in to Krova, pick a Space, and approve the connection. Access is limited to that Space, with your permissions in it.

Setup guides: Claude and ChatGPT.

Claude Code (remote)

With an API key:

claude mcp add --transport http krova https://krova.cloud/mcp --header "Authorization: Bearer kro_..."

Leave out --header to sign in with OAuth instead.

Other MCP clients

Send your API key in an Authorization: Bearer kro_... header on each request to https://krova.cloud/mcp.

The local stdio setup below is unchanged and still supported.

Client setup

All clients use the same launch command (npx -y @krovacloud/mcp) and the same environment variables. Set at least KROVA_API_KEY; set KROVA_SPACE_ID too if you want the Cube tools to default to one Space.

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config, or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS / %APPDATA%\Claude\claude_desktop_config.json on Windows) and add:

{

"mcpServers": { "krova": { "command": "npx", "args": ["-y", "@krovacloud/mcp"], "env": { "KROVA_API_KEY": "kro_your_api_key_here", "KROVA_SPACE_ID": "space_optional_default" } } } }

Restart Claude Desktop. The Krova Cloud tools appear under the tools (🔨) menu.

Claude Code

Add the server with one command:

claude mcp add krova \

--env KROVA_API_KEY=kro_your_api_key_here \ --env KROVA_SPACE_ID=space_optional_default \ -- npx -y @krovacloud/mcp

Or add it to .mcp.json in your project root (checked in, shared with your team):

{

"mcpServers": { "krova": { "command": "npx", "args": ["-y", "@krovacloud/mcp"], "env": { "KROVA_API_KEY": "kro_your_api_key_here", "KROVA_SPACE_ID": "space_optional_default" } } } }

Verify with claude mcp list.

Cursor

Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{

"mcpServers": { "krova": { "command": "npx", "args": ["-y", "@krovacloud/mcp"], "env": { "KROVA_API_KEY": "kro_your_api_key_here", "KROVA_SPACE_ID": "space_optional_default" } } } }

Then enable the krova server in Cursor Settings → MCP.

Any other MCP client

Any client that speaks MCP over stdio works — launch npx -y @krovacloud/mcp with the environment variables set. The config shape above is portable across VS Code (Copilot), Windsurf, Zed, and custom agents built on the MCP SDK.

Configuration

The server is configured entirely through environment variables:

Tools

All 37 tools, their parameters, and what they do. Every tool's spaceId is optional when KROVA_SPACE_ID is set.

Every tool advertises MCP annotations so your client can treat them appropriately: the sixteen read tools (list_cubes, get_cube, get_cube_ssh, list_regions, list_images, get_pricing, list_domains, get_domain_records, list_snapshots, list_backups, get_backup, list_backup_shares, list_tcp_mappings, list_webhooks, get_webhook, list_webhook_deliveries) are marked read-only, while the nine destructive tools (create_cube, delete_cube, delete_domain, delete_snapshot, restore_cube, share_backup, accept_backup_share, delete_tcp_mapping, delete_webhook) are marked destructive. update_domain mutates but is idempotent and reversible, so it is not. Most MCP clients surface a confirmation prompt before running a destructive tool — keep that confirmation on, since an LLM driven by untrusted content could be induced to call one.

The backup tools need the Backups permissions on the API key's member: View Backups to read, Manage Backups to share and answer shares. There is deliberately no download tool: the download link fetches the whole disk with no further authentication, and a model's conversation is the wrong place for it. Use krova backups download from the CLI.

create_cube parameters

| image | string | OS image slug — s