cloud.krova/mcp
Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.
Links
README
From the repo.
krova-node
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.
| Package | npm | What it is |
|---|---|---|
packages/sdk | @krovacloud/sdk | Typed TypeScript SDK for the Krova Cloud API |
packages/cli | @krovacloud/cli | The krova CLI (pure Node — built on the SDK) |
packages/mcp | @krovacloud/mcp | MCP server for Claude/Cursor/etc. |
packages/webhook | @krovacloud/webhook | Outbound-webhook signature verification |
packages/n8n-node | n8n-nodes-krova | n8n community node |
Develop
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.
Config for your environment
Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.
Tool
OS
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "{MCP_ENDPOINT_URL}"
}
}
}Paste into mcpServers in the config file. Restart Cursor after saving.
If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.