Official description7 sourcesMCP servers8d ago

krovacloud/krova-node

Provision and manage Krov

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add krova-node -- npx -y krova-node

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 0 ★ · krovacloud/krova-node · read from the repository page · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score: score 703 · 7 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository krovacloud/krova-node；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

krova-node

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

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