Odel
MCP server: One MCP server.

Krova Cloud MCP

@krovaRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.

Cloud infrastructurev0.3.15MITTypeScript
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: moves money, runs code or commands, deletes data, or sends messages for you.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@krovacloud/mcpv0.3.15

Run

npx -y @krovacloud/mcp

MCP client config

{
  "mcpServers": {
    "krova-cloud-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@krovacloud/mcp"
      ]
    }
  }
}
README1 min read

krova-node

krova-node MCP server

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.

PackagenpmWhat it is
packages/sdk@krovacloud/sdkTyped TypeScript SDK for the Krova Cloud API
packages/cli@krovacloud/cliThe krova CLI (pure Node — built on the SDK)
packages/mcp@krovacloud/mcpMCP server for Claude/Cursor/etc.
packages/webhook@krovacloud/webhookOutbound-webhook signature verification
packages/n8n-noden8n-nodes-krovan8n community node

Develop

sh
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.

Similar modules

Browse Cloud infrastructure