Krova Cloud MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Krova Cloud microVM provisioning and lifecycle operations: Do validated Cube operations remain scoped to the selected space and API-key authority as cloud tooling grows?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Provisioning and managing Krova Cloud Firecracker microVMs from MCP clients.

What we know

Official Krova Cloud stdio MCP exposing Space-scoped Cube, domain, snapshot, networking and power-management operations.

Maintenance / activity evidence

@krovacloud/mcp 0.3.15 published 2026-09-27T03:25:45.901Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Space membership permissions inherited by API key. Writes: Create/delete Cubes; Power operations; Create/delete snapshots/domains/network mappings.
Krova API key.
Sensitive access: Cloud infrastructure, SSH connection info, API key

Write-capable cloud provisioning can create costs and expose SSH endpoints; least-privilege keys are essential.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do validated Cube operations remain scoped to the selected space and API-key authority as cloud tooling grows?

The bounded review of the publisher's documented Krova Cloud microVM provisioning and lifecycle operations and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Write-capable cloud provisioning can create costs and expose SSH endpoints; least-privilege keys are essential.
Space membership permissions inherited by API key.
Krova API key.
Cloud-resource metadata and connection info are returned to the client.
Reviewed write actions: Create/delete Cubes; Power operations; Create/delete snapshots/domains/network mappings
Sensitive access: Cloud infrastructure, SSH connection info, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires Krova Cloud API key.
Create operations can incur cloud charges.
Permissions inherit the membership that created the key.

Original activity observations

@krovacloud/mcp 0.3.15 published 2026-09-27T03:25:45.901Z

Technical identity

npm/@krovacloud/mcp

Exact implementation source: https://www.npmjs.com/package/@krovacloud/mcp ↗
Reviewed resource type: MCP Server
Repository identity: krovacloud/krova-node
Package identity: npm:@krovacloud/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

Package registry ↗
@krovacloud/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
krovacloud/krova-node
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
KROVA_API_KEY required; KROVA_SPACE_ID optional default.
publisher install or stdio launch · Publisher instructions
npx -y @krovacloud/mcp

Configure / authenticate

MCP100 setup guide

Requires KROVA_API_KEY; KROVA_SPACE_ID is optional, used for Cube Space default.

claude desktop or cursor mcpServers json · MCP100 composed guide

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

Check connection
Suggested check
Once KROVA_API_KEY is set and the host starts npx server, inspect read-only workspace/catalog tools; do not create spaces or jobs.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `krovacloud`, run `claude mcp remove krovacloud` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Krova Cloud official MCP how-to explicitly confirms keys are per Space and deleting a key from Space settings revokes it immediately. Unregister the client separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove krovacloud

Official Documentation & Sources

What it does

Official Krova Cloud stdio MCP exposing Space-scoped Cube, domain, snapshot, networking and power-management operations.

Capability: Cloud & DevOps
Resource type: MCP Server
Best fit: Provisioning and managing Krova Cloud Firecracker microVMs from MCP clients.

Representative uses

List/get microVMs
Create/delete/power Cubes
Manage snapshots/domains/TCP mappings
Retrieve SSH connection data

Limitations

Requires Krova Cloud API key.
Create operations can incur cloud charges.
Permissions inherit the membership that created the key.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Krova API key.
Permissions: Space membership permissions inherited by API key.
Data handling: Cloud-resource metadata and connection info are returned to the client.
Cost: usage_based
Risk and cautions: Write-capable cloud provisioning can create costs and expose SSH endpoints; least-privilege keys are essential.

Access scope and cautions

Write actions: Create/delete Cubes Power operations Create/delete snapshots/domains/network mappings
Sensitive access: Cloud infrastructure SSH connection info API key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List/get microVMs; Create/delete/power Cubes; Manage snapshots/domains/TCP mappings; Retrieve SSH connection data.

What setup and authentication are documented?

Recorded installation/entrypoint step: KROVA_API_KEY=kro_... npx -y @krovacloud/mcp. Recorded transport: stdio. Recorded environment-variable notes: KROVA_API_KEY; KROVA_SPACE_ID optional; KROVA_BASE_URL optional. No configuration values are supplied here. Prerequisites: Node.js >=18. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Space-scoped Krova API key.

Can it modify data or perform write operations?

Documented write actions include: Create/delete Cubes; Power operations; Create/delete snapshots/domains/network mappings. Recorded permission boundary: Space membership permissions inherited by API key.

What data-handling boundary should I consider?

Cloud-resource metadata and connection info are returned to the client. Recorded sensitive-access context: Cloud infrastructure; SSH connection info; API key.

What limitations and risks should I check before use?

Write-capable cloud provisioning can create costs and expose SSH endpoints; least-privilege keys are essential. Requires Krova Cloud API key. Create operations can incur cloud charges. Permissions inherit the membership that created the key. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

Krova Cloud is listed as First-party MCP in MCP100’s current evidence.