cloud.krova/mcp
Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.
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.
Installation
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @krovacloud/mcpSet up in your AI client
Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"cloud-krova-mcp": {
"command": "npx",
"args": [
"-y",
"@krovacloud/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencePackage
@krovacloud/mcpnpmCompatible MCP Clients
cloud.krova/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
- Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect. - Cursor
~/.cursor/mcp.jsonRestart Cursor for changes to take effect. - VS Code
.vscode/mcp.jsonReload VS Code window for changes to take effect. - Windsurf
~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect. - Claude Code
.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.